exist-development — eXist Developer's List

Re: [Exist-development] svn commit

[Dmitriy S. <sha...@gm...>]

Ok, that happens -)

On Sat, Mar 3, 2012 at 9:22 AM, Joe Wicentowski <jo...@gm...> wrote:

>
> Sorry!  I didn't want the whole folder, just some files.  I used the
> oXygen SVN client to select all of them and clicked "commit" - and
> didn't realize it would do them all separately.  Once I realized what
> it was doing, I couldn't stop it.  Oh well...
>
>
-- 
Dmitriy Shabanov

Re: [Exist-development] svn commit

[Joe W. <jo...@gm...>]

Hi Dmitriy,

Sorry!  I didn't want the whole folder, just some files.  I used the
oXygen SVN client to select all of them and clicked "commit" - and
didn't realize it would do them all separately.  Once I realized what
it was doing, I couldn't stop it.  Oh well...

Joe

On Fri, Mar 2, 2012 at 11:20 PM, Dmitriy Shabanov <sha...@gm...> wrote:
>
> Hello,
>
> I do see that you doing a lot of small commits. That is not a problem, but you can save time if set folder as commit target. That will make one commit with all changers that you made in that folder.
>
> --
> Dmitriy Shabanov

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

> All tests now pass!
>
> Joe:  Go ahead and merge into stable if you want...

Nice work, Andrzej!  I hit a problem with my 'svn merge' routine -
which I emailed this list about.  As soon as I get that cleared up
I'll merge your changes and the updated documentation into stable.

Joe

[Exist-development] Xpath error/problem in trunk!

[Andrzej J. T. <an...@ch...>]

Wolfgang:

I've been trying to get my code running under the latest version of trunk (2.1)....but have run into
a weird xpath error.

I've attached both a text.xql file and test.xml file.  Put them in /db and then execute the test.xql.

It dies with the following exception:

	cannot convert xs:boolean('false') to a node set

Now if you look at the rather complex xpath statement, if you remove both the exists() and
normalize-space() comparisons at the end, it works.  Also works if you remove the "and @extension =
$id" clause....or if you remove the "@root = "2.16.840.1.113883.4.98" and" clause.

Very strange behaviour.  This is valid xpath...and worked fine in the older 1.5 version I used in
the past.  Almost seems like there is something going on with the parser or the optimizer that is
causing this weird error.

I'm not conversant with the query/xpath engine, so was hoping you could take a look.  Hopefully this
test case will let you replicate the issue.

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] ANT tasks to change/set permissions?

[Andrzej J. T. <an...@ch...>]

Dannes:

> the modified ANT task still shows an issue in the junit test suite. Please remember to run "build.sh
> test" before committing……. even to trunk.
> 
> the TeamCity log:
> [au:antunit] Target: test_Chmod  caused an ERROR
> [au:antunit]     at line 14, column 60
> [au:antunit]     Message: Syntax error in permissions: group=+read,other=+read
> [au:antunit]     took 0,005 sec

Just fixed this and checked it into trunk.

Apologies....I got the test backwards, mainly because the original comment was not worded very well
and so I got the two cases reversed.

All tests now pass!

Joe:  Go ahead and merge into stable if you want...


-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

Hi Dannes,

> the modified ANT task still shows an issue in the junit test suite. Please
> remember to run "build.sh test" before committing……. even to trunk.

Yikes.  It's probably a good idea that I didn't succeed in merging
Andrzej's commits in to 2.0.x stable!  I'll hold off until he has
addressed this.

Joe

[Exist-development] Porting changes from trunk to stable/2.0.x

[Joe W. <jo...@gm...>]

Hi all,

I've been trying to merge Andrzej's ant work in trunk to 2.0.x.  I am using
Wolfgang's suggested technique, which worked for me in the past but which
isn't working for me now.  Here was his technique:

> let's say you want to copy revision 10 from trunk to 1.4.x, assuming
> that you are currently in the 1.4.x directory:
>
> svn merge -r 9:10
https://exist.svn.sourceforge.net/svnroot/exist/trunk/eXist .

Here is what I did this time to merge Andrzej's revision 15960 into 2.0.x.
 On my Mac, in the terminal, inside the 2.0.x directory, I typed this
command:

  $ svn merge -r 15959:15960
https://exist.svn.sourceforge.net/svnroot/exist/trunk/eXist .

The response:

  svn: '
https://jo...@ex.../svnroot/exist/stable/eXist-2.0.x'
isn't in the same repository as '
https://exist.svn.sourceforge.net/svnroot/exist'

Does anyone have any tips for me to successfully perform the merge?

Thanks,
Joe

Re: [Exist-development] ANT tasks to change/set permissions?

[Dannes W. <da...@ex...>]

Hi,  

the modified ANT task still shows an issue in the junit test suite. Please remember to run "build.sh test" before committing……. even to trunk.

the TeamCity log:
[au:antunit] Target: test_Chmod  caused an ERROR
[au:antunit]     at line 14, column 60
[au:antunit]     Message: Syntax error in permissions: group=+read,other=+read
[au:antunit]     took 0,005 sec  

cheers

Dannes

--  
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624


On Sunday, 26 February 2012 at 4:51 , Joe Wicentowski wrote:

> Great, I understand now. I just have one final question: Does the new
> "permissions" attribute for chmod still allow the alternate format
> (quoting from the current docs):
>  
> [user|group|other]=[+|-][read|write|execute]
> For example, to set read and write permissions for the group, but
> not for others:</para>
> <synopsis>group=+read,+write,other=-read,-write
>  
> ? Or does it only take the flat 'rwxrwxrwx' style?  

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

Hi Andrzej,

Great, I understand now.  I just have one final question: Does the new
"permissions" attribute for chmod still allow the alternate format
(quoting from the current docs):

  [user|group|other]=[+|-][read|write|execute]
  For example, to set read and write permissions for the group, but
not for others:</para>
     <synopsis>group=+read,+write,other=-read,-write

?  Or does it only take the flat 'rwxrwxrwx' style?

Thanks,
Joe


On Sat, Feb 25, 2012 at 3:55 PM, Andrzej Jan Taramina
<an...@ch...> wrote:
> Joe:
>
>>   "The mode attribute on the chown ANT task is deprecated, but still
>> works for backwards compatibility.  Please convert your ANT scripts to
>> use the new permissions attribute instead. If both are specfied, then
>> the permissions attribute is the only one used."
>>
>> I looked and didn't see any changes to "chown" in your commit, only to
>> "chmod".  ("chown" doesn't even take a "mode" attribute.)  Did you
>> mean "chmod"?
>
> Sorry....my mistake. I meant chmod!
>
>> Also, you said to "use the new permissions attribute
>> instead", but did you add a new permissions attribute to "chmod"?  Or
>> are you suggesting that people stop using "chmod" altogether, and
>> instead modify their scripts to use "store" or "create" with the
>> "permissions" attribute?
>
> I added a new permissions attribute to chmod.
>
> so you can do either of the following for the chmod ANT task:
>
> <exist:chmod .....  permissions="rwxr--r--"/>
> <exist:chmod .....  mode="rwxr--r--"/>
>
> If you specify both, only the permissions= will be used.
>
>> Thanks in advance for clarifying this.  Once I understand this, I'll
>> update the documentation accordingly.
>
> Thanks for doing the docs!
>
>> Sure, I'll be happy to merge your ant task enhancements into
>> stable/exist-2.0.x along with my revisions to the ant task
>> documentation.  I plan do this when I have the documentation revisions
>> done.
>
> Much appreciated!
>
>
> --
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

Hi Andrzej,

>> I would be happy to add documentation to the ant-tasks.xml file to
>> include this new "permissions" attribute for the "store" and "create"
>> tasks.  Just let me know.
>
> Sure....I'm pretty tied up right now, so if you don't mind taking that on, that would be a big help.

I just committed an update to the ant tasks documentation, containing
information about the new permissions attribute on the store and
create tasks.  But I have a question about the 2nd part of your
changes.  You wrote:

  "The mode attribute on the chown ANT task is deprecated, but still
works for backwards compatibility.  Please convert your ANT scripts to
use the new permissions attribute instead. If both are specfied, then
the permissions attribute is the only one used."

I looked and didn't see any changes to "chown" in your commit, only to
"chmod".  ("chown" doesn't even take a "mode" attribute.)  Did you
mean "chmod"?  Also, you said to "use the new permissions attribute
instead", but did you add a new permissions attribute to "chmod"?  Or
are you suggesting that people stop using "chmod" altogether, and
instead modify their scripts to use "store" or "create" with the
"permissions" attribute?

Thanks in advance for clarifying this.  Once I understand this, I'll
update the documentation accordingly.

>> I can't see any other tasks that need this "permissions" attribute, can you?
>
> No...between the Create/Store and the Chmod, I think we pretty much have all the bases covered.

Cool.

>> Also, I noticed one other area in the ant tasks documentation that I
>> assume needs to be updated (no pun intended):
>>
>> The chmod task (http://exist-db.org/exist/ant-tasks.xml#d14366e1667)
>> continues to refer to "update" permissions instead of "execute"
>> permissions.
>
> That should probably be changed as well.

Great, I changed this in my commit above.

>> We should make sure that both the updated ant tasks and the updated
>> documentation is committed to stable/exist-2.0.x.
>
> Agreed....I'm kinda into upgrading our eXist app (very complex....seems that whenever there are
> major eXist changes, I'm the "canary in the coalmine" in finding subtle and complex bugs) to the
> latest trunk. I've already found some bugs that are showstoppers, things like exceptions in complex
> xpath expressions that worked fine before and are OK according to the xpath specs.
>
> So if you feel like backporting the new stuff to stable, be my guest, 'cause I'm unlikely to get to
> it very soon.

Sure, I'll be happy to merge your ant task enhancements into
stable/exist-2.0.x along with my revisions to the ant task
documentation.  I plan do this when I have the documentation revisions
done.

Cheers,
Joe

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

Hi Andrzej,

>>>> I don't think there are "direct" security management tasks but you can always run an XQuery script
>>>> with an ant task that changes the permissions and groups of any collections and resources.
>>>
>>> That's a bit awkward.  I think I'll write some ANT tasks to do this directly.
>
> I checked in the code to Trunk yesterday.
>
> Still have to update the documentation of the ANT task through.  But in a nutshell, you can now
> specify permissions="rwxr--r--" for the Create and Store ANT tasks for collections/resources
> respectively.

Thank you so much!  I just tested store and create using the
permissions attribute, and it worked perfectly.

I would be happy to add documentation to the ant-tasks.xml file to
include this new "permissions" attribute for the "store" and "create"
tasks.  Just let me know.

I can't see any other tasks that need this "permissions" attribute, can you?

Also, I noticed one other area in the ant tasks documentation that I
assume needs to be updated (no pun intended):

The chmod task (http://exist-db.org/exist/ant-tasks.xml#d14366e1667)
continues to refer to "update" permissions instead of "execute"
permissions.

We should make sure that both the updated ant tasks and the updated
documentation is committed to stable/exist-2.0.x.

Again, many thanks,
Joe

[Exist-development] Xpath error/problem in trunk!

[Andrzej J. T. <an...@ch...>]

Wolfgang:

I've been trying to get my code running under the latest version of trunk (2.1)....but have run into
a weird xpath error.

I've attached both a text.xql file and test.xml file.  Put them in /db and then execute the test.xql.

It dies with the following exception:

	cannot convert xs:boolean('false') to a node set

Now if you look at the rather complex xpath statement, if you remove both the exists() and
normalize-space() comparisons at the end, it works.  Also works if you remove the "and @extension =
$id" clause....or if you remove the "@root = "2.16.840.1.113883.4.98" and" clause.

Very strange behaviour.  This is valid xpath...and worked fine in the older 1.5 version I used in
the past.  Almost seems like there is something going on with the parser or the optimizer that is
causing this weird error.

I'm not conversant with the query/xpath engine, so was hoping you could take a look.  Hopefully this
test case will let you replicate the issue.

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

[Exist-development] Names of collections and resources in eXist-db

[Hungerburg <pc...@my...>]

I stumbled upon this, when I stored to /webdav a resource with a plus 
sign in its name, and could not fetch it from /rest. After some 
research, the issue has taken on an even bigger shape:

eXist seems to me to store resources by their url-encoded names. This 
only becomes apparent though, if the plain name and the url-encoded name 
are not the same, eg when the plain name contains plus or hash signs or 
two-byte utf-8 chars.

Resources stored this way cannot be fetched by the name, that was used 
to store them, because in effect eXist-db did rename them. Some examples 
that can be reproduced just using the admin collections panel "create 
collection" form, and looking at the listing returned:

Terms:
- face value is what I see printed on the listing page,
- input value is the value in the checkbox input form field, which one
sees in the page source,
- link target is the text in the anchor href, the link
to download the resource

# create a collection   "_ü_"
- face value:           "_ü_"
- input value:     "_%C3%BC_"
- link target: "_%25C3%25BC_"

# create a collection   "_+_"
- face value:           "_+_"
- input value:        "_%2B_"
- link target:      "_%252B_"

# create a collection   "_#_"
- face value:           "_#_"
- input value:        "_%23_"
- link target:      "_%2523_"

My guess is, that, what I call "input value", is the name of the 
collection, as stored in the db. Clearly - knowing that %25 is the 
url-encoding of the % sign, there is double encoding happening for the 
link target, because "_%2523_" will not request "_#_", instead it will 
request "_%23_". The name has changed.

Actually, this post here is just a plug for 
https://sourceforge.net/tracker/?func=detail&atid=117691&aid=3466454&group_id=17691 
- But I want to again bring this to the attention of all of you, because 
the scope grew, and because I consider this a bug, that 2.0 should not 
ship with.

Thank You

Peter

PS: One should be aware, that a raw # hash sign in a reources name will 
break the db in a way, it will not boot anymore, while + plus signs or 
two byte utf-8 will only be stored with wrong names.

[Exist-development] Problem changing admin password....

[Andrzej J. T. <an...@ch...>]

Running latest trunk...trying to get caught up.

Normally, I used an ant task to change the admin users password, with a task that looks like this:

<exist:password failonerror="false" uri="${exist.url}/xmlrpc/db" user="admin" password=""
name="admin" secret="${password}"/>

This used to work fine...but now it doesn't seem to do anything.  Is this a bug or oversight?

Also, you can't seem to change the admin password using the admin web page any more either.  You
can't see nor specify the group for the admin account if you try to edit it, so changing the
password fails.  Smells like another bug to me. ;-)

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] ANN: Release candidate eXist-db 1.4.2

[Dannes W. <da...@ex...>]

Hi,

On Fri, Feb 17, 2012 at 9:02 AM, Dannes Wessels <da...@ex...> wrote:

> Yesterday I posted a release candidate of eXist-db 1.4.2 on sourceforge (
> http://sourceforge.net/projects/exist/files/Stable/1.4.2/ ); this version
> will be the last of the 1.4.x series.
>
> If you think some patches are missing or some other functionality, please
> contact me. I plan to release the final version somewhere next week.
>

A list of changes since 1.4.1 will be published soon.

cheers

Dannes

-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] ANN: Release candidate eXist-db 1.4.2

[Adam R. <ad...@ex...>]

Dannes, perhaps you could explain also for everyone what 1.4.2 is and what
changes it contains?
On Feb 17, 2012 8:03 AM, "Dannes Wessels" <da...@ex...> wrote:

> All,
>
> Yesterday I posted a release candidate of eXist-db 1.4.2 on sourceforge (
> http://sourceforge.net/projects/exist/files/Stable/1.4.2/ ); this version
> will be the last of the 1.4.x series.
>
> If you think some patches are missing or some other functionality, please
> contact me. I plan to release the final version somewhere next week.
>
> Kind regards
>
> Dannes
>
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

[Exist-development] ANN: Release candidate eXist-db 1.4.2

[Dannes W. <da...@ex...>]

All,

Yesterday I posted a release candidate of eXist-db 1.4.2 on sourceforge (
http://sourceforge.net/projects/exist/files/Stable/1.4.2/ ); this version
will be the last of the 1.4.x series.

If you think some patches are missing or some other functionality, please
contact me. I plan to release the final version somewhere next week.

Kind regards

Dannes

-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] ANT tasks to change/set permissions?

[Joe W. <jo...@gm...>]

>> I don't think there are "direct" security management tasks but you can always run an XQuery script
>> with an ant task that changes the permissions and groups of any collections and resources.
>
> That's a bit awkward.  I think I'll write some ANT tasks to do this directly.

Wonderful!  That'll be a great addition to the ant task library.

Joe

Re: [Exist-development] ANT tasks to change/set permissions?

[Andrzej J. T. <an...@ch...>]

Dan:

> I don't think there are "direct" security management tasks but you can always run an XQuery script
> with an ant task that changes the permissions and groups of any collections and resources.

That's a bit awkward.  I think I'll write some ANT tasks to do this directly.


-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] ANT tasks to change/set permissions?

[Dan M. <dan...@gm...>]

I don't think there are "direct" security management tasks but you can
always run an XQuery script with an ant task that changes the permissions
and groups of any collections and resources.

- Dan

On Thu, Feb 16, 2012 at 10:32 AM, Andrzej Jan Taramina
<an...@ch...>wrote:

> Adam:
>
> Are there ANT tasks available to change/set permissions/ownership for
> collections/documents under
> the new security implementation?
>
> Thanks.
>
> --
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552

[Exist-development] ANT tasks to change/set permissions?

[Andrzej J. T. <an...@ch...>]

Adam:

Are there ANT tasks available to change/set permissions/ownership for collections/documents under
the new security implementation?

Thanks.

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] New stable branch: 2.0.x

[Dmitriy S. <sha...@gm...>]

On Thu, Feb 16, 2012 at 2:18 PM, Adam Retter <ad...@ex...> wrote:

> Actually may I suggest that developers do not merge to 2.0x stable. If we
> want a high quality release one person should manage this, I am happy to be
> that person. Howvere I will only merge where commit messages are clear, so
> developers must write clear tagged and descriptive messages. I would like
> to see us move to git in the near future so that we could control this with
> pull requests.
>
+++ on git ... but I don't want mail war -))

-- 
Dmitriy Shabanov

Re: [Exist-development] New stable branch: 2.0.x

[Adam R. <ad...@ex...>]

Actually may I suggest that developers do not merge to 2.0x stable. If we
want a high quality release one person should manage this, I am happy to be
that person. Howvere I will only merge where commit messages are clear, so
developers must write clear tagged and descriptive messages. I would like
to see us move to git in the near future so that we could control this with
pull requests.
On Feb 15, 2012 11:43 AM, "Wolfgang Meier" <wol...@ex...> wrote:

> To all committers and users: to prepare for the final 2.0 release and
> to continue with active development, we have created a new stable
> branch in SVN, which will replace the 1.4.x branch:
> stable/eXist-2.0.x.
>
> Developers: starting with rev 15855, please decide which commits have
> to be ported to 2.0.x and merge them yourselves. It is difficult for
> us if we have to go through the commit list months later to find the
> changes which have to be merged. As a general guideline, changes
> should be ported to the stable branch if they: 1) fix a bug which
> affects many users and the impact of the bug fix on other areas of
> eXist is limited, 2) fix an issue or improve a feature in code you are
> maintaining and which is sufficiently separate from eXist core, e.g.
> in an extension, 3) documentation updates, web site fixes. If in
> doubt, please send a message to the development list.
>
> Wolfgang
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

Re: [Exist-development] missing jars in eXist eclipse project

[Chris T. <chr...@gm...>]

Hello again,

There's simply no accounting for the stupid things I can come up with. I was thinking of GIT versus SVN - scratch the maven comments - I guess there's some nice integration of maven and eclipse.

Chris


On Feb 16, 2012, at 2:38 PM, Chris Tomlinson wrote:

> Dannes,
> 
> Thank you for the reply.
> 
> I've deleted the items from the .classpath that represent the jar files for optional items that are not enbled by default - all of the missing items that I listed - and eclipse shows no problems and the ./build.sh rebuild proceeds to a successful conclusion.
> 
> It seems to me that the key is to not commit to SVN (or maven I would assume) a .classpath that lists items that are not part of the configuration. At least that seems to be working for me just now with the eXist-2.0.x.
> 
> I don't know anything about maven but I don't see how that would change what the contents of the .classpath should be in relation to the checked out configuration no matter how the configuration is checked out.
> 
> Thjanks,
> Chris
> 
> 
> 
> On Feb 16, 2012, at 2:18 PM, Dannes Wessels wrote:
> 
>> 2012/2/16 Chris Tomlinson <chr...@gm...>
>> I should have included in the list the ojdbc14.jar - I have that lying about and put it in place - downloading that one can not be usefully automated, but it should also not be required by the default .classpath (there's a note about the jar file in the build.properites so anyone wanting to enable the option can deal with updating their local .classpath).
>> 
>> Chris , thank you for figuring out which files are missing. I realize that eclipse cannot deal well with missing JAR files, but it does not provide a way to really deal with it. In the end, when we switch to Maven, thngs would be much better.
>> 
>> cheers
>> 
>> Dannes
>> (netbeans user :-) )
>> 
>> -- 
>> eXist-db Native XML Database - http://exist-db.org
>> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 

Re: [Exist-development] missing jars in eXist eclipse project

[Chris T. <chr...@gm...>]

Dannes,

Thank you for the reply.

I've deleted the items from the .classpath that represent the jar files for optional items that are not enbled by default - all of the missing items that I listed - and eclipse shows no problems and the ./build.sh rebuild proceeds to a successful conclusion.

It seems to me that the key is to not commit to SVN (or maven I would assume) a .classpath that lists items that are not part of the configuration. At least that seems to be working for me just now with the eXist-2.0.x.

I don't know anything about maven but I don't see how that would change what the contents of the .classpath should be in relation to the checked out configuration no matter how the configuration is checked out.

Thjanks,
Chris



On Feb 16, 2012, at 2:18 PM, Dannes Wessels wrote:

> 2012/2/16 Chris Tomlinson <chr...@gm...>
> I should have included in the list the ojdbc14.jar - I have that lying about and put it in place - downloading that one can not be usefully automated, but it should also not be required by the default .classpath (there's a note about the jar file in the build.properites so anyone wanting to enable the option can deal with updating their local .classpath).
> 
> Chris , thank you for figuring out which files are missing. I realize that eclipse cannot deal well with missing JAR files, but it does not provide a way to really deal with it. In the end, when we switch to Maven, thngs would be much better.
> 
> cheers
> 
> Dannes
> (netbeans user :-) )
> 
> -- 
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624