[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261647#comment-13261647 ]
Steven Rowe commented on SOLR-3405: ----------------------------------- bq. Didn't try the above plugin but from the description I see it attaches jars directly to reactor's classpath, bypassing regular dependency resolution? I haven't tried it yet either, but yes, I too think it's bypassing regular dependency resolution. However, it's hooking into Ivy's capabilities, which makes me think this could be a long term solution for Lucene/Solr. > maven artifacts should be equivalent to binary packaging > -------------------------------------------------------- > > Key: SOLR-3405 > URL: https://issues.apache.org/jira/browse/SOLR-3405 > Project: Solr > Issue Type: Task > Components: Build > Reporter: Robert Muir > Fix For: 4.0 > > > Lets take the commons-csv scenario: > * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar > anywhere, > in fact it contains no third party jars (the stuff present in solr/lib) at > all. > * binary distribution contains only the jars necessary for *solrj* and > *contrib plugins*, and a solr.war > I think the maven artifacts should match whats in the binary release (no > third party jars > inside the .war are "exposed", we just publish the .war itself). This exposes > a lot less surface area. -- 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org