[
https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263125#comment-13263125
]
Steven Rowe commented on SOLR-3405:
-----------------------------------
{quote}
Maybe... a possible compromise here would be to continue pushing to
Maven central, but as a downstream event (after a release) within this
project. Meaning, the PMC votes on the "original" sources/convenience
binaries, but then the Maven experts around here can separately (once
the vote passes) take that binary release, expand it, attach POMs,
etc., and push to Maven central. This would mean the PMC doesn't vote
on what's-pushed-to-Maven, but we continue using this project's
infrastructure (svn, continuous builds, Jira, etc.) to push to Maven
central. Could something like that work?
{quote}
>From the Apache board perspective, I suspect that this would be viewed as a
>distinction without a difference; that is, no matter whether the PMC votes on
>Maven artifacts, the fact that they would be hosted by the Lucene/Solr
>project, and for the foreseeable future anyway, published by a PMC member, the
>PMC will continue to carry responsibility for Mavenish things when they go
>wrong.
That said, I'd be fine with this. The only (slight) snag: Maven artifacts have
to be signed; for the .jars/.war that's not a problem - they can be taken from
the binary distribution. The POMs, by contrast, will have to be separately
signed by a Lucene/Solr PMC member.
The PMC is supposed to only be voting on source releases anyway, right?
> 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.1
>
>
> 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
