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
>