On 17 Jun 07, at 4:24 PM 17 Jun 07, Brett Porter wrote:
On 18/06/2007, at 1:52 AM, Jason van Zyl wrote:
If you're working on a fix that requires a specific fix and is not
something that is in ongoing, high-flux development then can
people release first and then incorporate.
Two example of late are plexus-utils in trunk, and the Maven
parent POM.
Snapshots are for intra-project, high-flux development. Having
them as external dependencies is not good. We either have to
change repository settings around which sucks, or things are very
well tested. For the Maven parent POM I can't use it in the branch
because it's not released, and it causes a CCE in the remote-
resources plugin (Kulp, you may want to look at that, it's a CCE
between and ArtifactRepository and
org.apache.maven.model.Repository).
I don't think there's any problem with pushing out tons of micro
releases and just makes things far more stable (and releasable).
I was going to take care of that very shortly, but wanted to make
sure it was at least correct first. Using v5 was not - the gpg
plugin that was included did not work with the assemblies (as you
can see from your staging repository: http://people.apache.org/
~jvanzyl/maven-2.0.7-staging-repository/org/apache/maven/maven/
2.0.7/ - the signatures are all missing -src).
It won't work on the assemblies anyway because that's not the name we
use for distribution so the signatures would not be correct. They
have to be taken as they are built with the final name and those are
signed. Something I need to bring up as a best practice discussion.
They way we do things currently we cannot do a release from end to
end. The assembly we make are "maven-core" or "maven-embedder" when
they are deployed to the repository. The module making the assembly
must be named "maven" if we want it to work. Or we need to be able to
make the assembly from the top-level directory like we do for the
source assembly.
As I understood it, you weren't going to do anything from the
branch again. If I'd known that, I'd have suggested you stage and
release the parent too.
I'll call a vote on it today.
There is something wrong with the remote resources plugin as
specified in the parent POM. It passes in
org.apache.maven.model.Repository to the artifact resolution
mechanism when it expects an ArtifactRepository which leads to a CCE.
So it's not ready to go out yet.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
