[jsword-devel] [JIRA] Commented: (JS-140) Use Ivy to manage JSword's dependencies.
DM Smith (JIRA)
jira at crosswire.org
Sun Dec 5 17:13:37 MST 2010
[ http://www.crosswire.org/bugs/browse/JS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645#action_13645 ]
DM Smith commented on JS-140:
-----------------------------
A little bit frustrating so far.
I created an ivy.xml file for jsword with the dependencies. It does stuff I don't expect.
It includes jars, I guess as "transitive" dependencies, of stuff that JSword does not use. It appears one can explicitly exclude stuff. I'd rather one could explicitly include stuff and everything else is ignored.
It puts the files outside of where Eclipse can see it. It seems it is possible to change this.
It's not clear to me how to use these jars within ant for a build.
Into a ~/.ivy2/cache/... folder with a horrible pathing system. It seems it is possible to change this, but I've not seen any example so far.
It grabs javadoc, which is entirely not needed. Any IDE worth it's salt can construct from the source.
Then it cannot find some of what we use:
jdom 1.1.1 (it can find 1.1)
jaf 1.1 (it can find 1.0.2) Current version of jaf is 1.1.1.
xerces 2.11 (it can find 2.9)
icu4j 4.6 (we were using 4.4.2) (it can find a much earlier one)
Part of the not finding stuff is that it is recently released. Ok, I get that. But the rest? E.g. JAF, ICU4.4.2.
So we'll need a mechanism to hold stuff we need earlier.
Ultimately, using ivy means buying into maven as the core way to obtain 3-rd party jars. Running ivy essentially sets up a local maven repository and serves files out of it.
I did see that it is easy to publish the collection of jars as a maven 2 structured repository. That should be a plus.
> Use Ivy to manage JSword's dependencies.
> ----------------------------------------
>
> Key: JS-140
> URL: http://www.crosswire.org/bugs/browse/JS-140
> Project: JSword
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: DM Smith
> Assignee: DM Smith
> Priority: Minor
>
> Ivy is an Apache component that is tightly integrated with Ant that will grab dependent jars and provide them to the project.
> This would greatly reduce the SVN repository size going forward as we would no longer need to house these libraries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.crosswire.org/bugs/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jsword-devel
mailing list