maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: [VOTE] Release Maven Enforcer version 1.0.1 - Take 2
Date Fri, 17 Jun 2011 14:57:13 GMT
+1


LieGrue,
strub

--- On Fri, 6/17/11, Kristian Rosenvold <kristian.rosenvold@gmail.com> wrote:

> From: Kristian Rosenvold <kristian.rosenvold@gmail.com>
> Subject: Re: [VOTE] Release Maven Enforcer version 1.0.1 - Take 2
> To: "Maven Developers List" <dev@maven.apache.org>
> Date: Friday, June 17, 2011, 6:38 AM
> I am aware of that problem, I did not
> know how to fix it. If you know how to do it better, please
> help.  I will test it ;)
> 
> I was happy that the project site staged consistently and
> without manual intervention according to standard maven
> deployment procedure. Unless there actually
> is a policy that we *must* stage to version-specific areas
> (as opposed to a recommendation) I'll keep this vote open.
> 
> After all, most previous sites for enforcer seem to have
> been staged on the flipside of napkins ;)
> 
> Kristian
> 
> 
> 
> Den 17.06.2011 08:26, skrev Lukas Theussl:
> > 
> > hrm, sorry but I think there is actually a problem now
> with the stage site. In r1136499 [1] you removed the version
> number from the staging location. I'm not sure if there is a
> formal rule but we usually stage the RC sites at a unique
> location that is kept after the release for reference. For
> instance:
> > 
> > http://maven.apache.org/plugins/maven-surefire-plugin-2.9/
> > http://maven.apache.org/plugins/maven-surefire-plugin-2.8/
> > http://maven.apache.org/plugins/maven-surefire-plugin-2.7/
> > 
> > etc.
> > 
> > The staging location you specified now will be
> overwritten at the next release. Problem is I'm not sure if
> relative links will work with the versioned locations, I
> will try to find a minute today to test.
> > 
> > sigh... :(
> > 
> > -Lukas
> > 
> > 
> > [1] http://svn.apache.org/viewvc?view=revision&revision=1136499
> > 
> > 
> > Kristian Rosenvold wrote:
> >> Hi,
> >> 
> >> The release includes the enforcer-plugin,
> enforcer-rules and
> >> enforcer-api modules. The site-staging problems
> from take 1 were fixed
> >> in r1136499. The only diff between this vote and
> take 1 is the site
> >> deployment.
> >> 
> >> 
> >> We solved 2 issues:
> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=16879
> 
> >> 
> >> There are still a couple of issues left in JIRA:
> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MENFORCER+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
> 
> >> 
> >> 
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-011/
> >> 
> >> Staging site:
> >> http://maven.apache.org/staging/plugins/maven-enforcer-plugin/
> >> 
> >> Guide to testing staged releases:
> >> http://maven.apache.org/guides/development/guide-testing-releases.html
> >> 
> >> Vote open for 72 hours.
> >> 
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >> 
> >> And here's my +1
> >> 
> >> Kristian
> >> 
> >> 
> >> 
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >> 
> > 
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 

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


Mime
View raw message