[
https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261669#comment-13261669
]
Robert Muir commented on SOLR-3405:
-----------------------------------
And in the idea above, obviously -sources.jar and -javadocs.jar are "exempt",
as they
are maven-specific and not in the binary packaging. Thats fine: I'm talking
about
the actual binary jars. Our checking script would exclude those.
I think currently these are "the same" in the sense that
they are built from the same code, but currently have timestamp differences as
they
are pulled from build/.
On the non-maven side there are improvements like this as well: for example I
think
the lucene jars used by solr are "rebuilt" in the process. But i think it would
be
more ideal if solr 'prepare-release', when populating the jar, populated these
lucene
jars from lucene's binary release in dist/ the same way: so they are the exact
same
jars that were released in the lucene binary distribution.
I dont think this stuff has to be done immediately, and i know its complicated
and being
really pedantic, but I think it would be a good step.
> 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: [email protected]
For additional commands, e-mail: [email protected]
