You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/03/04 21:33:41 UTC

Re: making releases was: [VOTE] Release maven-plugin-tools 2.1

On 04/03/2007, at 6:41 AM, Dennis Lundberg wrote:

> Can you point to some specific Apache rule that says so? There have  
> been discussions on this topic before, but I have yet to see  
> someone point me to the source for this rule. I don't disagree with  
> the sentiment of this, I just want to know where the rulebook is:)

Yep, as Jason pointed out, it's a Maven rule, not an Apache one.

IMO, you complied with it by stating the rev and providing the  
appropriate binary. I think we have a stated intent to use staged  
release artifacts instead, but until the tools work completely I  
think the 'old process' is just fine.

However, Daniel is right in that they are missing the necessary  
license files, so I'll vote on the thread -1.

>
>> For Jason's instructions, see:
>> http://maven.apache.org/developers/release/releasing.html
>
> I'm aware of these instructions. As it is now however, its a PITA  
> to do it that way because of the "contact Jason" part of it. Every  
> release is depending on Jason to copy over the artifacts, because  
> the repositorytools isn't working as they should over scp:. I  
> thought that I'd take a bit of load off Jason's shoulders by doing  
> it the "old way".

I used the old way for surefire as Jason said the tools weren't  
working when I asked and I found it less error prone than copying  
over by hand. Sounds like they might be fixed but until that makes it  
into a released version.

- Brett

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