lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3943) Use ivy cachepath and cachefileset instead of ivy retrieve
Date Tue, 03 Apr 2012 21:52:28 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245788#comment-13245788
] 

Hoss Man commented on LUCENE-3943:
----------------------------------

"ant example" doesn't run the example, so it can't use any ephemeral classpaths that ant creates
on the fly.  "ant example" currently sets up the example files (ie: copying the war to where
jetty will look for it) hence my point that it could copy the jars as needed in order for
jetty & solr to find them

(the example has to work in the binary build via "java -jar start.jar" even if users don't
have any of the original build.xml files)
                
> Use ivy cachepath and cachefileset instead of ivy retrieve
> ----------------------------------------------------------
>
>                 Key: LUCENE-3943
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3943
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Chris Male
>
> In LUCENE-3930 we moved to resolving all external dependencies using ivy:retrieve.  This
process places the dependencies into the lib/ folder of the respective modules which was ideal
since it replicated the existing build process and limited the number of changes to be made
to the build.
> However it can lead to multiple jars for the same dependency in the lib folder when the
dependency is upgraded, and just isn't the most efficient way to use Ivy.
> Uwe pointed out that _when working from svn or in using src releases_ we can remove the
ivy:retrieve calls and make use of ivy:cachepath and ivy:cachefileset to build our classpaths
and packages respectively, which will go some way to addressing these limitations -- however
we still need the build system capable of putting the actual jars into specific lib folders
when assembling the binary artifacts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message