[jsword-devel] [JIRA] Commented: (JS-218) maven build should not depend on crosswire maven repos

DM Smith (JIRA) jira at crosswire.org
Sun Apr 15 12:09:14 MST 2012


    [ http://www.crosswire.org/bugs/browse/JS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25677#comment-25677 ] 

DM Smith commented on JS-218:
-----------------------------

A bit of historical background:
When we started the maven servers didn't seem to be reliable and not everything we used was present.
We wanted a place to store our snapshots.
I could not find jlfgr.jar in maven. This is used by BibleDesktop for its images. I've been looking to eliminate it for something else.
jdom was not current enough in maven for Android. Only recently did it get there.
xerces/xalan, which JSword will use if present are notoriously out of date.
icu4j-charsets are not in maven. JSword will use these if present.
maven is out of date wrt icu4j.
Until recently, maven did not keep current with the Lucene releases.

Having our own repository solved these issues.

I understand that it is a good thing to get jsword into maven central and that we'll do what is necessary for that.



> maven build should not depend on crosswire maven repos
> ------------------------------------------------------
>
>                 Key: JS-218
>                 URL: http://www.crosswire.org/bugs/browse/JS-218
>             Project: JSword
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.6
>            Reporter: Douglas Campos
>            Assignee: Douglas Campos
>             Fix For: 1.6.1
>
>
> having <repository> tags on pom.xml is forbidden for inclusion at maven central

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jsword-devel mailing list