Martin wrote:

There were advantages in having the jars under the jar folder, where they were before. There are only a few jars and it means the eclipse project works instantly after checkout. Will the jars still be there?

No, they wouldn't. Only the jars that are not found via ivy/maven.

You are right that it won't be instantaneous. It might cause people to wonder what's wrong. So clear documentation is needed.

I think the basic pattern for those that don't do Eclipse is to run ant first. We have several.

I'll attach a patch to the issue so we can play with it, comment on it and get it right.

Projects that depend upon the jsword Eclipse project will be correct once jsword is built via ant.

The bigger problem I have with this mechanism is that of reliability:

• It relies on crosswire.org and other servers. While we have problems every now and then with the crosswire.org server, this introduces more of a problem.
• The jars gotten via ivy are not checked against the keys gotten from their original distribution source. We cannot know whether they are complete and untampered with.

I'm also concerned with how it works while not being connected to the internet.

For the sake of getting about a dozen jars I would like to vote for the easiest method, which in my opinion was putting them in the jar folder.

Patch for build.xml, core.xml and new file ivy.xml

This has been done. I'm leaving it open to iterate any other changes that need to be done. Feel free to make it better. Or talk about what should be done to make it better. Note, maven may come later. Right now, I'm trying to solve the problem of storing jars in source code control.

Ivy now manages JSword's 3-rd party dependencies.