[ https://issues.apache.org/jira/browse/SOLR-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712223#action_12712223 ]
Shalin Shekhar Mangar commented on SOLR-831: -------------------------------------------- This issue is now invalid after SOLR-900. Now solr-core does not contain solrj and there is no solr-commons jar anymore. Hoss's comment on moving the source folders remains valid. But I think we can mark this one as resolved/invalid. > revist jar packaging prior to next release > ------------------------------------------ > > Key: SOLR-831 > URL: https://issues.apache.org/jira/browse/SOLR-831 > Project: Solr > Issue Type: Bug > Components: clients - java > Affects Versions: 1.3 > Reporter: Hoss Man > Assignee: Shalin Shekhar Mangar > Fix For: 1.4 > > > as noted on the mailing list... > http://www.nabble.com/Solr-1.3-Maven-Artifact-Problem-to20132273.html#a20132273 > {noformat} > I am using the Solr 1.3 mave nartifacts from [1]. It seems that these > artifacts are > not correct. I have noticed that: > 1) solr-core artifact contains org.apache.solr.client.solrj packages, and at > the same > time, the solr-core artifact depends on the solr-solrj artifact. > {noformat} > at a minimum we should resolve this discrepancy, but more generally we should > consider moving anything currently in solrj that solr "core" has a > compile/run dependency on into solr-common ... possibly to the point of > eliminating the solr-solrj jar altogether. > marking fix for 1.4 as a reminder to consider/decide before the next release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.