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?<br><br><div class="gmail_quote">
On 6 December 2010 05:33, DM Smith (JIRA) <span dir="ltr"><<a href="mailto:jira@crosswire.org">jira@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
[ <a href="http://www.crosswire.org/bugs/browse/JS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646#action_13646" target="_blank">http://www.crosswire.org/bugs/browse/JS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646#action_13646</a> ]<br>
<div class="im"><br>
DM Smith commented on JS-140:<br>
-----------------------------<br>
<br>
</div>I've figured out how<br>
* to include only the stuff that is wanted. Now it only brings in the jar itself and the source jar. It just took adding conf="default->master,sources" to the dependency.<br>
* to specify a different location for the cache. Now at jsword/ivy.<br>
* to put the jars in a useful place: jsword/lib (this solves the caching problem)<br>
* to blend jars we can't get via ivy, with those from ivy<br>
<br>
This introduced a ripple effect and the build files (core.xml and jsword's build.xml) needed to change:<br>
* changed ${target.jar} to point to "lib"<br>
* uncommented prepare.extra to use it in jsword's build.xml to load dependencies.<br>
* made clean in core.xml clean out the ${target.jar} directory<br>
<br>
What's left:<br>
clean up the jsword-web documentation explaining how to checkout the project and use it within Eclipse.<br>
<br>
The big gotcha, upon checkout one must run ant in the jsword project. Otherwise, Eclipse (and probably other IDE's) will complain. If Eclipse is run first, then jsword will have to be refreshed after the run.<br>
<br>
FYI, I just noticed that there is an ant task to convert an ivy definition to a maven pom.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
> Use Ivy to manage JSword's dependencies.<br>
> ----------------------------------------<br>
><br>
> Key: JS-140<br>
> URL: <a href="http://www.crosswire.org/bugs/browse/JS-140" target="_blank">http://www.crosswire.org/bugs/browse/JS-140</a><br>
> Project: JSword<br>
> Issue Type: Improvement<br>
> Affects Versions: 1.6<br>
> Reporter: DM Smith<br>
> Assignee: DM Smith<br>
> Priority: Minor<br>
><br>
> Ivy is an Apache component that is tightly integrated with Ant that will grab dependent jars and provide them to the project.<br>
> This would greatly reduce the SVN repository size going forward as we would no longer need to house these libraries.<br>
<br>
--<br>
This message is automatically generated by JIRA.<br>
-<br>
If you think it was sent incorrectly contact one of the administrators: <a href="http://www.crosswire.org/bugs/secure/Administrators.jspa" target="_blank">http://www.crosswire.org/bugs/secure/Administrators.jspa</a><br>
-<br>
For more information on JIRA, see: <a href="http://www.atlassian.com/software/jira" target="_blank">http://www.atlassian.com/software/jira</a><br>
<br>
<br>
<br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</div></div></blockquote></div><br>