release process: says to use maven-release-plugin:2.0-beta-9 but latest parent pom defines 2.0-beta-8

The lastest version according to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/ is version 13 Which defines the maven-release-plugin as 2.0-beta-8 But the http://maven.apache.org/developers/release/releasing.html documentation says to use 2.0-beta-9. Is the documentation j

[VOTE] Release Maven Eclipse plugin version 2.7 (take 2)

Note: * Changed wording of index.html as per Arnaud suggestion. * Added source-release assembly Hi, We solved 11 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/

Re: [VOTE] Release Maven Eclipse plugin version 2.7

Ok here are the steps I took: Copied https://svn.apache.org/repos/asf/maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml to src/assemble/ Modified pom to include maven-assembly-plugin

docs developers/release/releasing.html needs new screen shots.

I've updated http://maven.apache.org/developers/release/releasing.html but the screen shots need redoing. Is the person who first cut them able to redo them please? (probably Brian Fox since his username is in the images) - To u

Re: Bouncy Castle Jars

Hi Carlos, I passed what you said on to the Bouncy Castle guys, but they said: > It's pretty simple. We publish to our website. That's it. We don't > particularly mind that other people might want to publish via Maven. > > The fact that others might want to use Maven is excellent, however w

Re: [VOTE] Release Maven Eclipse plugin version 2.7 (take 2)

Barrie Treloar wrote: * Added source-release assembly Staging repo: https://repository.apache.org/content/repositories/maven-staging-006/ It appears the source-release packages are missing the LICENSE and NOTICE files [0]. The descriptor you copied isn't fully worked out yet. For a plugin,

Re: Bouncy Castle Jars

Just don't use their stuff then, clearly they don't want to make it easy for users. On Sun, Jun 7, 2009 at 5:19 AM, Tim Pizey wrote: > Hi Carlos, > > I passed what you said on to the Bouncy Castle guys, but they said: > > > It's pretty simple. We publish to our website. That's it. We don't >

Re: docs developers/release/releasing.html needs new screen shots.

What part doesn't match the screenshots? I updated them last time there were any significant changes. On Sun, Jun 7, 2009 at 4:49 AM, Barrie Treloar wrote: > I've updated http://maven.apache.org/developers/release/releasing.html > but the screen shots need redoing. > > Is the person who first cu

Re: Bouncy Castle Jars

If someone is interested in maintaining the poms and tracking their releases, we can set up a repository at oss.sonatype.org. On Sun, Jun 7, 2009 at 6:57 AM, Brian Fox wrote: > Just don't use their stuff then, clearly they don't want to make it easy > for users. > > > On Sun, Jun 7, 2009 at 5:19

Re: Bouncy Castle Jars

On Sun, Jun 7, 2009 at 3:18 PM, Brian Fox wrote: > If someone is interested in maintaining the poms and tracking their > releases, we can set up a repository at oss.sonatype.org. a lot of apache projects rely on bouncy castle releases for crypto. i'd be willing to help maintain an off shore reposi

Re: Bouncy Castle Jars

ok create a "new project" issue here: https://issues.sonatype.org/browse/OSSRH and those interested in maintaining it can add a comment to the issue to get privs. On Sun, Jun 7, 2009 at 7:30 AM, Robert Burrell Donkin < robertburrelldon...@gmail.com> wrote: > On Sun, Jun 7, 2009 at 3:18 PM, Brian

Re: release process: says to use maven-release-plugin:2.0-beta-9 but latest parent pom defines 2.0-beta-8

The version in the pom is the locked down version for our plugins to use. The latest release plugin is 2.0-beta-9: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/ You can override that version in your pom if you are releasing a plugin...we don't update the parent every

Re: Bouncy Castle Jars

On Sun, Jun 7, 2009 at 3:37 PM, Brian Fox wrote: > ok create a "new project" issue here: > https://issues.sonatype.org/browse/OSSRH and those interested in maintaining > it can add a comment to the issue to get privs. please take a quick look at https://issues.sonatype.org/browse/OSSRH-39 and see

Re: docs developers/release/releasing.html needs new screen shots.

On Sun, Jun 7, 2009 at 11:30 PM, Brian Fox wrote: > What part doesn't match the screenshots? I updated them last time there were > any significant changes. > > On Sun, Jun 7, 2009 at 4:49 AM, Barrie Treloar wrote: > >> I've updated http://maven.apache.org/developers/release/releasing.html >> but t

Re: release process: says to use maven-release-plugin:2.0-beta-9 but latest parent pom defines 2.0-beta-8

On Mon, Jun 8, 2009 at 12:10 AM, Brian Fox wrote: > The version in the pom is the locked down version for our plugins to use. > The latest release plugin is 2.0-beta-9: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/ > > You can override that version in your pom if yo

Re: [VOTE] Release Maven Eclipse plugin version 2.7 (take 2)

On Sun, Jun 7, 2009 at 10:15 PM, Benjamin Bentmann wrote: > Barrie Treloar wrote: > >> * Added source-release assembly >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-staging-006/ > > It appears the source-release packages are missing the LICENSE and NOTICE > files [

[VOTE] Release Maven Eclipse plugin version 2.7 (take 3)

(source-release should be correct now) Hi, We solved 11 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11133&resolu