Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Loren C. <lor...@gm...> - 2013-08-13 17:05:40
|
Here is a simple upload.html for testing the template. <div xmlns="http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" data-template="templates:surround" data-template-with="templates/page.html" data-template-at="content" data-template-options="noscript=yes"> <xf:model> <xf:instance xmlns=""> <data> <file filename="" mediatype="" size=""/> </data> </xf:instance> <xf:bind nodeset="/data/file" type="xs:anyURI"/> <xf:submission id="load" resource="{$restxq}upload" method="put" replace="none" ref="//file"> <xf:message ev:event="xforms-submit-done" level="ephemeral">file uploaded.</xf:message> <xf:message ev:event="xforms-submit-error" level="ephemeral">An error occurred.</xf:message> </xf:submission> </xf:model> <div class="row-fluid"> <div id="content" class="span12"> <div class="page-header"> <h1 data-template="config:app-title">Generated page</h1> </div> <div class="alert alert-success">adad</div> <xf:upload ref="/data/file" accept="application/zip,.xsd"> <xf:filename ref="@filename"/> <xf:mediatype ref="@mediatype"/> <xf:size ref="@size"/> <xf:send ev:event="xforms-value-changed" submission="load"/> </xf:upload> <br/> <xf:output ref="/data/file/@filename"> <xf:label>File: </xf:label> </xf:output> <br/> <xf:output ref="/data/file/@mediatype"> <xf:label>Media: </xf:label> </xf:output> <br/> <xf:output ref="/data/file/@size"> <xf:label>Size: </xf:label> </xf:output> <br/> <xf:output ref="/data/file"> <xf:label>Content: </xf:label> </xf:output> </div> </div> </div> On Aug 13, 2013, at 12:53 PM, Loren Cahlander <lor...@gm...> wrote: > If you go to http://greatlinkup.com:8080/exist/apps/schema/tsgen.html you will see the navbar is messed up. > > <munged.png> > > If I comment out the xf:upload, I get: > > <noupload.png> > > I have been looking through the CSS files and cannot find the problem. > |
|
From: Loren C. <lor...@gm...> - 2013-08-13 16:54:02
|
If you go to http://greatlinkup.com:8080/exist/apps/schema/tsgen.html you will see the navbar is messed up. If I comment out the xf:upload, I get: I have been looking through the CSS files and cannot find the problem. |
|
From: Loren C. <lor...@gm...> - 2013-08-07 21:03:34
|
The schemas in the schemas folder are mostly lacking namespaces |
|
From: Alain C. <ala...@ag...> - 2013-08-01 10:08:25
|
Sometimes, attributes or elements contain a value which is a qualified name. The corresponding namespace might not be "used" elsewhere but should not be dropped... -Alain Le 01/08/2013 11:44, Adam Retter a écrit : > > Why do you think it is a bug? Check XML serialization specs... > > On 1 Aug 2013 10:27, "Вячеслав Седов" <sch...@gm... > <mailto:sch...@gm...>> wrote: > > at least for me it look like bug even if someone call it 'feature' > > with best wishes, > Slav > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-development > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Вячеслав С. <sch...@gm...> - 2013-08-01 09:56:45
|
i have for example xslt with template match="namespace:element" but no one element from this ns exist in this xslt - it`s common practice so if i save xslt to db and it become invalid - i am not sure it good idea to drop "unused" ns 2013/8/1 Adam Retter <ad...@ex...>: > Why do you think it is a bug? Check XML serialization specs... > > On 1 Aug 2013 10:27, "Вячеслав Седов" <sch...@gm...> wrote: >> >> at least for me it look like bug even if someone call it 'feature' >> >> with best wishes, >> Slav >> >> >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Adam R. <ad...@ex...> - 2013-08-01 09:44:38
|
Why do you think it is a bug? Check XML serialization specs... On 1 Aug 2013 10:27, "Вячеслав Седов" <sch...@gm...> wrote: > at least for me it look like bug even if someone call it 'feature' > > with best wishes, > Slav > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
|
From: Вячеслав С. <sch...@gm...> - 2013-08-01 09:27:29
|
at least for me it look like bug even if someone call it 'feature' with best wishes, Slav |
|
From: Adam R. <ad...@ex...> - 2013-07-28 17:26:39
|
> This is very cool and very welcomed. I use git daily and think this is a > very good move. > > Can we assume that the svn repo will stay up for some time? I have ansible > scripts (ansiblework.com) that install exist on amazon ec2 instances and > will convert this to doing so from git. However I may not convert over to > git for a couple of weeks are we are in the final planning phase to go live > with a new public site with exist-db as the backend. Too many other things > to work on before go live. The svn repo is still there and will not go away for a while. However, head of the SVN repo is empty, instead you just need to pass an additional single argument to your 'svn co' command, which is '-r 18779'. e.g. "svn co -r 18779 https://svn.code.sf.net/p/exist/code/trunk/eXist" would get you the lastest code revision version of trunk that was in SVN before we moved to GitHub. > In consideration of this statement in the readme file > Note In the above example, we switch the checked out branch of eXist from > "develop" to "master". We are making use of GitFlow for eXist, and as such > "develop" is our current stable work in progress which will eventually > become the next release version, whereas "master" is always the last > released version. The choice of which to use is entirely yours. > > Will there be a way to clone a specific version of exist-db via git? Will > you tag versions and push the tags or will this ability not be there? Also > is there a file in the repo that contains the lastest version that is easily > parsed? Yes we will continue tag releases in Git just as we did in Svn. When you pull from the upstream repo into your fork you will receive any new tags as well, because really they are just a type of special branch. You can see the releases here - https://github.com/eXist-db/exist/releases Also GitHub provide a very nice API that you could call to get all sorts of information about the exist repo and its latest tags. See here http://developer.github.com/v3/git/tags/ > > Thanks > Eric P > > > > On Sat, Jul 27, 2013 at 8:53 PM, Joe Wicentowski <jo...@gm...> wrote: >> >> Congratulations, team eXist-db! I think this is new foundation will serve >> eXist-db well. >> >> Joe >> >> Sent from my iPhone >> >> On Saturday, July 27, 2013 at 5:00 PM, Adam Retter wrote: >> >> It is my absolute pleasure to announce that all of the eXist-db source >> code and associated projects have now been migrated from Subversion on >> SourceForge over to Git at GitHub https://github.com/eXist-db/exist. >> >> There is a good start to the documentation on how to work with the >> code from GitHub, take a look here - >> https://github.com/eXist-db/exist#information-for-developers >> >> The main changes (apart from Git), are that: >> >> 1) Where we had one Subversion repository before we now have several >> Git repositories. The main code base for eXist is now in the "exist" >> repo on our GitHub. For the exact mappings between Subversion and Git >> see here: https://github.com/eXist-db/svn2git-rules >> >> 2) We no longer allow direct commits to our repositories. Rather we >> make use of the excellent "Pull Request" functionality of GitHub. So >> if you would like to contribute, simply fork our repo, do your work >> and send us a Pull Request. >> >> 3) We are now using GitFlow on the main "exist" Git repo. Note this is >> not yet used for our other Git repos. This may appear to be difficult >> at first, but it is actually relatively simple and should allow us to >> better understand change and hopefully make the release process easier >> and more frequent. You can find more about this here: >> https://github.com/eXist-db/exist#contributing-to-exist >> >> Enjoy! >> >> Adam. >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> >> >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > > > > -- > KK4MWM (Ham Radio) > About Me > http://www.thingiverse.com/DaddyOh > Join the 3DPrinter Revolution > http://makerbot.com > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Dannes W. <di...@ex...> - 2013-07-28 15:24:32
|
On 28 Jul 2013, at 16:49 , Eric Palmer <er...@er...> wrote: > This is very cool and very welcomed. I use git daily and think this is a very good move. > > Can we assume that the svn repo will stay up for some time? the sf.net svn-repo is still there, but in the current state, it looks empty; a specific revision-id should be applied to retrieve the correct version from 'trunk'. > I have ansible scripts (ansiblework.com) that install exist on amazon ec2 instances and will convert this to doing so from git. However I may not convert over to git for a couple of weeks are we are in the final planning phase to go live with a new public site with exist-db as the backend. Too many other things to work on before go live. so it is possible, but with some additional svn parameters > > In consideration of this statement in the readme file > Note In the above example, we switch the checked out branch of eXist from "develop" to "master". We are making use of GitFlow for eXist, and as such "develop" is our current stable work in progress which will eventually become the next release version, whereas "master" is always the last released version. The choice of which to use is entirely yours. > > Will there be a way to clone a specific version of exist-db via git? Will you tag versions and push the tags or will this ability not be there? Also is there a file in the repo that contains the lastest version that is easily parsed it should be possible to clone a specific version from git, you'd need to use a specific hash for a specific branch. I'd say you need to have a hash from the 'master' (aka stable) branch..... cheers Dannes |
|
From: Eric P. <er...@er...> - 2013-07-28 14:49:22
|
This is very cool and very welcomed. I use git daily and think this is a very good move. Can we assume that the svn repo will stay up for some time? I have ansible scripts (ansiblework.com) that install exist on amazon ec2 instances and will convert this to doing so from git. However I may not convert over to git for a couple of weeks are we are in the final planning phase to go live with a new public site with exist-db as the backend. Too many other things to work on before go live. In consideration of this statement in the readme file *Note* In the above example, we switch the checked out branch of eXist from "develop" to "master". We are making use of GitFlow for eXist<https://github.com/eXist-db/exist#contributing-to-exist>, and as such "develop" is our current stable work in progress which will eventually become the next release version, whereas "master" is always the last released version. The choice of which to use is entirely yours. Will there be a way to clone a specific version of exist-db via git? Will you tag versions and push the tags or will this ability not be there? Also is there a file in the repo that contains the lastest version that is easily parsed? Thanks Eric P On Sat, Jul 27, 2013 at 8:53 PM, Joe Wicentowski <jo...@gm...> wrote: > Congratulations, team eXist-db! I think this is new foundation will > serve eXist-db well. > > Joe > > Sent from my iPhone > > On Saturday, July 27, 2013 at 5:00 PM, Adam Retter wrote: > > It is my absolute pleasure to announce that all of the eXist-db source > code and associated projects have now been migrated from Subversion on > SourceForge over to Git at GitHub https://github.com/eXist-db/exist. > > There is a good start to the documentation on how to work with the > code from GitHub, take a look here - > https://github.com/eXist-db/exist#information-for-developers > > The main changes (apart from Git), are that: > > 1) Where we had one Subversion repository before we now have several > Git repositories. The main code base for eXist is now in the "exist" > repo on our GitHub. For the exact mappings between Subversion and Git > see here: https://github.com/eXist-db/svn2git-rules > > 2) We no longer allow direct commits to our repositories. Rather we > make use of the excellent "Pull Request" functionality of GitHub. So > if you would like to contribute, simply fork our repo, do your work > and send us a Pull Request. > > 3) We are now using GitFlow on the main "exist" Git repo. Note this is > not yet used for our other Git repos. This may appear to be difficult > at first, but it is actually relatively simple and should allow us to > better understand change and hopefully make the release process easier > and more frequent. You can find more about this here: > https://github.com/eXist-db/exist#contributing-to-exist > > Enjoy! > > Adam. > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > -- KK4MWM (Ham Radio) About Me <http://about.me/ericpalmer> http://www.thingiverse.com/DaddyOh Join the 3DPrinter Revolution http://makerbot.com |
|
From: Adam R. <ad...@ex...> - 2013-07-28 09:58:10
|
Whoops! Sorry about that Jens, I made a mistake in the mapping file. I have now corrected it and re-converted the tamboti code, I think all should be fine now. Let me know if you see any more issues, I did check through the mappings file again just now, and that was the only issue I could see, but well 'many eyes' and all that... On 28 July 2013 03:40, oe...@gm... <oe...@gm...> wrote: > Looks like ziziphus is in tamboti and tamboti is nowhere. > > Jens > > Sent from my HTC > > > > ----- Reply message ----- > From: "W.S. Hager" <ws...@gm...> > To: "Adam Retter" <ad...@ex...> > Cc: "eXist development" <exi...@li...>, > "exi...@li..." <exi...@li...> > Subject: [Exist-open] [HEADS-UP] We have moved to GitHub > Date: Sun, Jul 28, 2013 00:26 > > > Hurray! > > > 2013/7/27 Adam Retter <ad...@ex...> >> >> It is my absolute pleasure to announce that all of the eXist-db source >> code and associated projects have now been migrated from Subversion on >> SourceForge over to Git at GitHub https://github.com/eXist-db/exist. >> >> There is a good start to the documentation on how to work with the >> code from GitHub, take a look here - >> https://github.com/eXist-db/exist#information-for-developers >> >> The main changes (apart from Git), are that: >> >> 1) Where we had one Subversion repository before we now have several >> Git repositories. The main code base for eXist is now in the "exist" >> repo on our GitHub. For the exact mappings between Subversion and Git >> see here: https://github.com/eXist-db/svn2git-rules >> >> 2) We no longer allow direct commits to our repositories. Rather we >> make use of the excellent "Pull Request" functionality of GitHub. So >> if you would like to contribute, simply fork our repo, do your work >> and send us a Pull Request. >> >> 3) We are now using GitFlow on the main "exist" Git repo. Note this is >> not yet used for our other Git repos. This may appear to be difficult >> at first, but it is actually relatively simple and should allow us to >> better understand change and hopefully make the release process easier >> and more frequent. You can find more about this here: >> https://github.com/eXist-db/exist#contributing-to-exist >> >> Enjoy! >> >> Adam. >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open > > > > > -- > > W.S. Hager > Lagua Web Solutions > http://lagua.nl > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Dave F. <dav...@gm...> - 2013-07-28 03:16:29
|
Hooray! :D On Sat, Jul 27, 2013 at 9:40 PM, oe...@gm... <oe...@gm...>wrote: > Looks like ziziphus is in tamboti and tamboti is nowhere. > > Jens > > Sent from my HTC > > > > ----- Reply message ----- > From: "W.S. Hager" <ws...@gm...> > To: "Adam Retter" <ad...@ex...> > Cc: "eXist development" <exi...@li...>, " > exi...@li..." <exi...@li...> > Subject: [Exist-open] [HEADS-UP] We have moved to GitHub > Date: Sun, Jul 28, 2013 00:26 > > > Hurray! > > > 2013/7/27 Adam Retter <ad...@ex...> > >> It is my absolute pleasure to announce that all of the eXist-db source >> code and associated projects have now been migrated from Subversion on >> SourceForge over to Git at GitHub https://github.com/eXist-db/exist. >> >> There is a good start to the documentation on how to work with the >> code from GitHub, take a look here - >> https://github.com/eXist-db/exist#information-for-developers >> >> The main changes (apart from Git), are that: >> >> 1) Where we had one Subversion repository before we now have several >> Git repositories. The main code base for eXist is now in the "exist" >> repo on our GitHub. For the exact mappings between Subversion and Git >> see here: https://github.com/eXist-db/svn2git-rules >> >> 2) We no longer allow direct commits to our repositories. Rather we >> make use of the excellent "Pull Request" functionality of GitHub. So >> if you would like to contribute, simply fork our repo, do your work >> and send us a Pull Request. >> >> 3) We are now using GitFlow on the main "exist" Git repo. Note this is >> not yet used for our other Git repos. This may appear to be difficult >> at first, but it is actually relatively simple and should allow us to >> better understand change and hopefully make the release process easier >> and more frequent. You can find more about this here: >> https://github.com/eXist-db/exist#contributing-to-exist >> >> Enjoy! >> >> Adam. >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > > > > -- > > W.S. Hager > Lagua Web Solutions > http://lagua.nl > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > -- David Finton |
|
From: <oe...@gm...> - 2013-07-28 02:40:46
|
Looks like ziziphus is in tamboti and tamboti is nowhere. Jens Sent from my HTC ----- Reply message ----- From: "W.S. Hager" <ws...@gm...> To: "Adam Retter" <ad...@ex...> Cc: "eXist development" <exi...@li...>, "exi...@li..." <exi...@li...> Subject: [Exist-open] [HEADS-UP] We have moved to GitHub Date: Sun, Jul 28, 2013 00:26 Hurray! 2013/7/27 Adam Retter <ad...@ex...> It is my absolute pleasure to announce that all of the eXist-db source code and associated projects have now been migrated from Subversion on SourceForge over to Git at GitHub https://github.com/eXist-db/exist. There is a good start to the documentation on how to work with the code from GitHub, take a look here - https://github.com/eXist-db/exist#information-for-developers The main changes (apart from Git), are that: 1) Where we had one Subversion repository before we now have several Git repositories. The main code base for eXist is now in the "exist" repo on our GitHub. For the exact mappings between Subversion and Git see here: https://github.com/eXist-db/svn2git-rules 2) We no longer allow direct commits to our repositories. Rather we make use of the excellent "Pull Request" functionality of GitHub. So if you would like to contribute, simply fork our repo, do your work and send us a Pull Request. 3) We are now using GitFlow on the main "exist" Git repo. Note this is not yet used for our other Git repos. This may appear to be difficult at first, but it is actually relatively simple and should allow us to better understand change and hopefully make the release process easier and more frequent. You can find more about this here: https://github.com/eXist-db/exist#contributing-to-exist Enjoy! Adam. -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open -- W.S. Hager Lagua Web Solutions http://lagua.nl |
|
From: Joe W. <jo...@gm...> - 2013-07-28 00:53:21
|
Congratulations, team eXist-db! I think this is new foundation will serve eXist-db well. Joe Sent from my iPhone On Saturday, July 27, 2013 at 5:00 PM, Adam Retter wrote: > It is my absolute pleasure to announce that all of the eXist-db source > code and associated projects have now been migrated from Subversion on > SourceForge over to Git at GitHub https://github.com/eXist-db/exist. > > There is a good start to the documentation on how to work with the > code from GitHub, take a look here - > https://github.com/eXist-db/exist#information-for-developers > > The main changes (apart from Git), are that: > > 1) Where we had one Subversion repository before we now have several > Git repositories. The main code base for eXist is now in the "exist" > repo on our GitHub. For the exact mappings between Subversion and Git > see here: https://github.com/eXist-db/svn2git-rules > > 2) We no longer allow direct commits to our repositories. Rather we > make use of the excellent "Pull Request" functionality of GitHub. So > if you would like to contribute, simply fork our repo, do your work > and send us a Pull Request. > > 3) We are now using GitFlow on the main "exist" Git repo. Note this is > not yet used for our other Git repos. This may appear to be difficult > at first, but it is actually relatively simple and should allow us to > better understand change and hopefully make the release process easier > and more frequent. You can find more about this here: > https://github.com/eXist-db/exist#contributing-to-exist > > Enjoy! > > Adam. > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > |
|
From: W.S. H. <ws...@gm...> - 2013-07-27 22:26:20
|
Hurray! 2013/7/27 Adam Retter <ad...@ex...> > It is my absolute pleasure to announce that all of the eXist-db source > code and associated projects have now been migrated from Subversion on > SourceForge over to Git at GitHub https://github.com/eXist-db/exist. > > There is a good start to the documentation on how to work with the > code from GitHub, take a look here - > https://github.com/eXist-db/exist#information-for-developers > > The main changes (apart from Git), are that: > > 1) Where we had one Subversion repository before we now have several > Git repositories. The main code base for eXist is now in the "exist" > repo on our GitHub. For the exact mappings between Subversion and Git > see here: https://github.com/eXist-db/svn2git-rules > > 2) We no longer allow direct commits to our repositories. Rather we > make use of the excellent "Pull Request" functionality of GitHub. So > if you would like to contribute, simply fork our repo, do your work > and send us a Pull Request. > > 3) We are now using GitFlow on the main "exist" Git repo. Note this is > not yet used for our other Git repos. This may appear to be difficult > at first, but it is actually relatively simple and should allow us to > better understand change and hopefully make the release process easier > and more frequent. You can find more about this here: > https://github.com/eXist-db/exist#contributing-to-exist > > Enjoy! > > Adam. > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- W.S. Hager Lagua Web Solutions http://lagua.nl |
|
From: Adam R. <ad...@ex...> - 2013-07-27 22:24:57
|
There has always been a plan to modularise eXist further and to create a set of Maven Modules, this is a good first step, I have personally ignored the work so far in the "mvn-repo" repo as it took its own approach and diverged from what the core team agreed in Prague, I guess we will remove it soon. These things will have to be reconciled at some point... On 27 July 2013 23:13, Casey Jordan <cas...@jo...> wrote: > Thanks Adam this is great! > > While we are on the subject, are there any plans to further separate the > codebase (Not necessarily into different repos)? I can see some clear > benefits to seperating at least the core src/, extensions/ and webapp/ > > It would also make maven-izing everything much easier ;) Something I have > wanted to do desperately for a while now and would be happy to help with. > > Cheers, > > Casey > > On Sat, Jul 27, 2013 at 5:02 PM, Omar Siam <si...@gm...> wrote: >> >> Cheers and thumbs up! 8-) >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development > > > > > -- > -- > Casey Jordan > easyDITA a product of Jorsek LLC > "CaseyDJordan" on LinkedIn, Twitter & Facebook > (585) 348 7399 > easydita.com > > > This message is intended only for the use of the Addressee(s) and may > contain information that is privileged, confidential, and/or exempt from > disclosure under applicable law. If you are not the intended recipient, > please be advised that any disclosure copying, distribution, or use of > the information contained herein is prohibited. If you have received > this communication in error, please destroy all copies of the message, > whether in electronic or hard copy format, as well as attachments, and > immediately contact the sender by replying to this e-mail or by phone. > Thank you. > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Casey J. <cas...@jo...> - 2013-07-27 22:13:25
|
Thanks Adam this is great! While we are on the subject, are there any plans to further separate the codebase (Not necessarily into different repos)? I can see some clear benefits to seperating at least the core src/, extensions/ and webapp/ It would also make maven-izing everything much easier ;) Something I have wanted to do desperately for a while now and would be happy to help with. Cheers, Casey On Sat, Jul 27, 2013 at 5:02 PM, Omar Siam <si...@gm...> wrote: > Cheers and thumbs up! 8-) > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- -- Casey Jordan easyDITA a product of Jorsek LLC "CaseyDJordan" on LinkedIn, Twitter & Facebook (585) 348 7399 easydita.com This message is intended only for the use of the Addressee(s) and may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, please be advised that any disclosure copying, distribution, or use of the information contained herein is prohibited. If you have received this communication in error, please destroy all copies of the message, whether in electronic or hard copy format, as well as attachments, and immediately contact the sender by replying to this e-mail or by phone. Thank you. |
|
From: Omar S. <si...@gm...> - 2013-07-27 21:02:15
|
Cheers and thumbs up! 8-) |
|
From: Adam R. <ad...@ex...> - 2013-07-27 21:00:10
|
It is my absolute pleasure to announce that all of the eXist-db source code and associated projects have now been migrated from Subversion on SourceForge over to Git at GitHub https://github.com/eXist-db/exist. There is a good start to the documentation on how to work with the code from GitHub, take a look here - https://github.com/eXist-db/exist#information-for-developers The main changes (apart from Git), are that: 1) Where we had one Subversion repository before we now have several Git repositories. The main code base for eXist is now in the "exist" repo on our GitHub. For the exact mappings between Subversion and Git see here: https://github.com/eXist-db/svn2git-rules 2) We no longer allow direct commits to our repositories. Rather we make use of the excellent "Pull Request" functionality of GitHub. So if you would like to contribute, simply fork our repo, do your work and send us a Pull Request. 3) We are now using GitFlow on the main "exist" Git repo. Note this is not yet used for our other Git repos. This may appear to be difficult at first, but it is actually relatively simple and should allow us to better understand change and hopefully make the release process easier and more frequent. You can find more about this here: https://github.com/eXist-db/exist#contributing-to-exist Enjoy! Adam. -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Jens Ø. P. <oe...@gm...> - 2013-07-22 09:36:10
|
Hi Dannes, Seeing that Dmitriy committed to a branch yesterday, is this restriction limited to commits to trunk, not to for instance apps? Best, Jens On Jul 18, 2013, at 12:06 PM, Dannes Wessels <da...@ex...> wrote: > All, > > yesterday evening we have tagged 'eXist-2.1' in the subversion code archive on sf.net ; this means that no further development will be done on 'trunk' of the eXist-db code; > > The next few days we'll be moving eXist-db to GitHub ; please hold your changes until the migration is done. > > Thnx > > Dannes > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Dannes W. <da...@ex...> - 2013-07-18 10:07:26
|
All, yesterday evening we have tagged 'eXist-2.1' in the subversion code archive on sf.net ; this means that no further development will be done on 'trunk' of the eXist-db code; The next few days we'll be moving eXist-db to GitHub ; please hold your changes until the migration is done. Thnx Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Dannes W. <da...@ex...> - 2013-06-11 10:04:52
|
Hi, On Mon, Jun 10, 2013 at 10:29 PM, <wol...@ex...> wrote: > > We should update .classpath accordingly then. > sure, but we need one to feel the 'owner' for the eclipse files, just like for netbeans/intellij; somehow nobody from the community takes this job :-( interestingly... these files could be easily generated out of something else..... cheers Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: <wol...@ex...> - 2013-06-10 20:29:33
|
> I've checked out the trunk from SVN and the .classpath references the following missing jars: * lib/endorsed/saxonhe-9.2.1.5.jar Saxon has been updated recently, so the entry indeed needs to be changed. > * extensions/modules/lib/sac-1.3.jar > * extensions/modules/lib/cssparser-0.9.5.jar Those jars are optional and only installed if you enable the corresponding modules (extensions/build.properties). > The code compiles if I remove these jars from the class path. We should update .classpath accordingly then. Wolfgang |
|
From: Chris H. <chr...@ya...> - 2013-06-10 20:08:37
|
Hi, Apologies if this is not the right forum for this. I've checked out the trunk from SVN and the .classpath references the following missing jars: * lib/endorsed/saxonhe-9.2.1.5.jar * extensions/modules/lib/sac-1.3.jar * extensions/modules/lib/cssparser-0.9.5.jar I'm reluctant to raise a bug in case I'm missing something as it's the first time I've tried to check out eXist-db for use in Eclipse. The code compiles if I remove these jars from the classpath. Am I right in thinking this is a bug or am I being an idiot? Thanks, Chris |
|
From: Loren C. <lor...@gm...> - 2013-06-04 19:19:52
|
Hello folks, I am in the process of creating an app that takes the URL to an XML Schema and creates a documentation view of the schema. It will include an SVG view of the particular sub item and a dynamically generated sample XML fragment of the same sub item. Please take a look at http://greatlinkup.com:8080/exist/apps/schema/index.html?schema=http://release.niem.gov/niem/niem-core/2.0/niem-core.xsd It is a work in progress, but I would appreciate any questions or suggestions. This will be made available to all. I am working on it from 9:00 a.m. - 5:00 p.m. EDT, so expect the occasional errors due to trying something. Thanks, Loren |
64 messages has been excluded from this view by a project administrator.
