lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Fri, 27 Apr 2012 19:04:50 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263890#comment-13263890
] 

Robert Muir commented on SOLR-3405:
-----------------------------------

{quote}
What changed your mind? (Serious question)
{quote}

Seriously: I want our releases clean and bulletproof from problems.

People can say we only vote on the source release, but we can't pretend that we are not
responsible for binary/maven artifacts we produce too. The commons-csv issue showed that
as a PMC we get hassled about these things too!

So when we put stuff up in people.apache.org/~whoever/staging_area/lucene-solr-XXX.YYY,
I want everything in that folder to be packaged correctly, not illegal, not causing
problems to other projects, etc, etc.

Its unrelated to the benefits of maven. I just want this stuff clean.

So I got frustrated with some of the responses/suggestions here that seem like maybe 
people aren't taking this stuff as seriously as we should be.

We are held responsible for the stuff we put out, so if people feel "anything goes"
for the maven artifacts as long as they work, then I don't know how we as a PMC are
supposed to have any confidence at all that they are clean!

You can say i'm being overly anal or a policeman or whatever, but I feel I have to
be watching this maven stuff like a hawk right now (even though i dont really understand
it). 

So it starts to become clear to me, that not everyone cares so much about the maven
artifacts being proper and correct. With that being the case, *I* don't want to be 
responsible for it, I'd just as soon absolve myself of it, get back to working on
search engines, and let someone else (not our PMC) be held to the fire for it.


                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message