lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <nicolas.lale...@hibnet.org>
Subject Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr
Date Tue, 24 Apr 2012 13:26:49 GMT

Le 24 avr. 2012 à 03:10, Benson Margulies a écrit :

> On Mon, Apr 23, 2012 at 8:42 PM, Chris Male <gento0nz@gmail.com> wrote:
>> I'm with Steve here, -1.  I think the arguments have already been well
>> articulated and the issue seems to be about dependency management in general
>> not just about Maven.  However I also absolutely agree with Robert that we
>> need to make this easier somehow.
>> 
>> One thing I thought, is there any way we can get our own repo? In
>> organisations that use Maven for their projects, that's how they tend to
>> handle this situation.  They have their own repo for dependencies they need
>> to manage and they use repo1 for the rest.   As an ASF project, do we get
>> any help in this regards?
> 
> Chris,
> 
> I'm getting a bit tired of reading my own writing here, and I bet a
> lot of other people are, too, so I'll try to answer your question
> concisely and then disappear from this for at least 12 hours.
> 
> The rule we are dealing with goes as follows, stated pseudo-biblically:
> 
> * No PMC shall publish a JAR file containing modified versions of some
> other PMC's output unless you change the package names.

Does this apply to any binary release in apache's dist, any tgz ? Or is it just for maven
?

Nicolas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message