incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Release candidate for M2 release
Date Thu, 01 Mar 2007 16:48:13 GMT


I really hate to do this to you, but as things stand right now, I'd 
probably have to -1 the maven artifacts.    I should have mentioned this 
before you tried cutting the candidates.  I've just been a bit busy.

I started a discussion on general@ last week about stuff that should be in 
the poms:<>

From that, the top level pom should probably be changed so:
1) It uses org.apache:apache:3 as the parent

2) Add a <inceptionYear>2006</inceptionYear> tag

3) All the poms should say "Apache Yoko ....", not just Yoko.

Also, nothing is properly GPG signed.   

I've gone ahead and attached a new top level pom.xml that fixes the above.   
It ALSO adds two new profiles:

1) deploy - adds the sources jar to all the builds so they will get 
deployed with the jar.   Eventually will add javadocs as well.

2) release - adds the gpg signing as well as the usage of a alternate 
deploy location for staging the artifacts.

Thus, you should be able to do:

mvn -Pruntime,deploy,release

to pretty much handle everything.   (That would then need to be documented 
on your wiki)


On Wednesday 28 February 2007 15:14, Rick McGuire wrote:
> I have created a branch for the M2 release candidate, and built a set of
> distribution artifacts from that branch.  The artifacts can be
> downloaded from:
> As discussed earlier, this is the distribution built using the runtime
> profile, so it only contains the core ORB and RMI support.  Please try
> to download and take a look to see if there are any problems, which
> should be fixed in the M2 branch.  I'll call a vote on releasing this
> tomorrow once people have had an opportunity to look at the first
> snapshot.
> Rick

J. Daniel Kulp
Principal Engineer
P: 781-902-8727    C: 508-380-7194

View raw message