lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <...@thetaphi.de>
Subject RE: discussion about release frequency.
Date Mon, 20 Sep 2010 16:54:39 GMT
If somebody reorders the directory structure, I will shout “revert revert revert” J

 

We can only “fully” support maven by switching to maven, but most of the core committers
don’t want this (including me). In my opinion, the approach we had was fine, to simply create
the jar files as we do for the binary release, but add some (hopefully) automatically generated
pom files to it.

 

One thing I don’t like in this release process (as it currently works) is non-repeatable
maven artifact generation. With maven, it’s impossible to regenerate the JAR files with
the *same* MD5, even the MD5’s of the jar files in the binary release zip are different
than the maven ones. If repeatability is not possible, at least the JAR files in the –bin.zip
should be identical to the maven released ones!

 

Uwe

 

-----

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

 <http://www.thetaphi.de/> http://www.thetaphi.de

eMail: uwe@thetaphi.de

 

From: Robert Muir [mailto:rcmuir@gmail.com] 
Sent: Monday, September 20, 2010 9:35 AM
To: dev@lucene.apache.org
Subject: Re: discussion about release frequency.

 

 

On Mon, Sep 20, 2010 at 12:29 PM, Ryan McKinley <ryantxu@gmail.com> wrote:

 

I'm not sure it would be useful yet.  There is consensus that the
process needs to improve.  The only concrete 'vote' i could imagine
now is to drop maven.

 

I completely agree the process needs to improve, but at the end of the day, if we are planning
to support maven officially in releases, i think we should vote on it becoming part of the
actual release process.

 

So maybe its premature to vote on this part, but at the same time, I have concerns about what
it would take to 'fully support' maven.

 

For example, if we have to reorganize our source tree to what it wants (src/main/java, src/main/test),
and rename our artifacts to what it wants (-SNAPSHOT, etc), this is pretty important. what
else might maven 'require'.

 

its also my understanding that in the past, when maven is upgraded (e.g. Maven 2), it might
require you to modify your project in ways such as this to fit its new "needs".

 

>From what I know of maven, its quite inflexible about such things, and I want to know
what i'm getting into before we claim to 'make maven first class citizen'.

 

-- 
Robert Muir
rcmuir@gmail.com


Mime
View raw message