[ https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224752#comment-13224752 ]
Steven Rowe commented on SOLR-3204: ----------------------------------- {quote} Option 2 is optional dependencies: http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html. This is a way to force the users of your artifacts to explicitly declare some or all of your dependencies, rather than getting them automatically. In other words, virality control. {quote} I don't like the fact that taking this approach for all of our non-Mavenized dependencies (by which I mean those that are not in Maven Central) would put a much greater burden on our users that consume Lucene/Solr artifacts via Maven. Users would have to either have to a) download the binary release and manually install the non-Maven artifacts one-by-one in their local or internal repository (after consulting both the top-level Maven POM and a list of per-module dependencies that currently only exists in a lib/ directory listing); or b) download the source release, run {{ant get-maven-poms}}, then run {{mvn -N -Pbootstrap install}}. Neither of these fall within the expected level of effort for Maven users. -1 from me for using optional dependencies to counter Maven's virality. > solr-commons-csv must not use the org.apache.commons.csv package > ---------------------------------------------------------------- > > Key: SOLR-3204 > URL: https://issues.apache.org/jira/browse/SOLR-3204 > Project: Solr > Issue Type: Bug > Components: Build > Affects Versions: 3.5 > Reporter: Emmanuel Bourg > Assignee: Uwe Schindler > Priority: Blocker > Fix For: 3.6 > > Attachments: SOLR-3204.patch, SOLR-3204.patch, SOLR-3204.patch, > SOLR-3204.patch, apache-solr-commons-csv-1.0-SNAPSHOT-r966014.jar, > apache-solr-commons-csv-1.0-SNAPSHOT-r966014.jar, rule.txt, rule.txt, > solr-csv.patch > > > The solr-commons-csv artifact reused the code from the Apache Commons CSV > project but the package wasn't changed to something else than > org.apache.commons.csv in the process. This creates a compatibility issue as > the Apache Commons team works toward an official release of Commons CSV. It > prevents Commons CSV from using its own org.apache.commons.csv package, or > forces the renaming of all the classes to avoid a classpath conflict. -- 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