Hello,
I agree.
But note I have missed something in the ASF pom
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<releaseProfiles>apache-release</releaseProfiles>
</configuration>
</plugin>
And I have added in two places a kind of warning for people to test
their settings configuration :
* http://www.apache.org/dev/publishing-maven-artifacts.html (Section
Test you settings )
* http://maven.apache.org/asf-pom/ (Section Settings Configuration)
And sure btw I don't have any issues about moving all doc provided by
Benson to the apache main website.
And revert all stuff.
At the end I just want most of people being happy (sure not an easy task :-) )
2011/2/9 Mark Struberg <strub...@yahoo.de>:
> Benson, the signing itself doesn't take that long, even for projects like
> OpenJPA which needs about 1 hour for the whole build. So I'm with Brian that
> it's better to spend 1 minute for the code signing in the prepare phase than
> having to revert tags, branches, rebuild all from scratch again, etc which in
> case of OpenJPA would cost you almost half a day.
>
> There are a few pro and con arguments here, but 'fail fast' is imo the way to
> go here.
>
> LieGrue,
> strub
>
> --- On Wed, 2/9/11, Benson Margulies <bimargul...@gmail.com> wrote:
>
>> From: Benson Margulies <bimargul...@gmail.com>
>> Subject: Re: svn commit: r1065772 - in /maven/pom/trunk: asf/pom.xml
>> maven/pom.xml
>> To: "Maven Developers List" <dev@maven.apache.org>
>> Date: Wednesday, February 9, 2011, 2:13 AM
>> Unfortunately for the coherence of
>> this discussion, it was months and
>> months ago that I filed the original version of this JIRA.
>> The best I
>> can lay my mental fingers on is this: for a large project,
>> signing and
>> such can take a very long time, making it very slow and
>> frustrating to
>> work through a set of problems. I was having a very hard
>> time
>> debugging problems in release:prepare, and the addition of
>> the profile
>> just added to my confusion.
>>
>> That all being written, if my first encounter with the
>> parent had been
>> documentation that explained what it was doing and why, I
>> would never
>> have filed the JIRA in the first place. Which is why I
>> already wrote,
>> and Olivier already committed, the explanatory material
>> that I offered
>> to write to save others from the confusion I encountered
>> when I first
>> used this parent. So if you all revert this change,
>> honestly, no more
>> squeaks from me.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
