You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Massol <vm...@pivolis.com> on 2004/05/01 12:24:32 UTC

Little glitches in rc2 release process

Hi Brett,

I think I've found some little glitches in the release process we've
used for rc2. This is just a heads up so that we can improve the process
for rc3.

- in several plugins there are wrong <version> tags. Here's what I
typically find:

    <version>
      <id>1.1</id>
      <name>1.1</name>
      <tag>HEAD</tag>
    </version>
    <version>
      <id>1.1</id>
      <name>1.1</name>
      <tag>MAVEN_ASPECTWERKZ_1_1</tag>
    </version>

Whereas it should be:

    <version>
      <id>1.1</id>
      <name>1.1</name>
      <tag>MAVEN_ASPECTWERKZ_1_1</tag>
    </version>
    <version>
      <id>1.2</id>
      <name>1.2</name>
      <tag>HEAD</tag>
    </version>

- It's missing the download link for the new version in navigation.xml.
For example, for the 1.1 release of aspectwerkz plugin:

    <menu name="Downloads">
      <item name="AspectWerkz plugin 1.0"
href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectwerkz-plugi
n-1.0.jar"/>
    </menu>

whereas it should have been:

    <menu name="Downloads">
      <item name="AspectWerkz plugin 1.0"
href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectwerkz-plugi
n-1.0.jar"/>
      <item name="AspectWerkz plugin 1.1"
href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectwerkz-plugi
n-1.1.jar"/>
    </menu>

- Sometimes, the new versions have not been created in the JIRA project.
Say I'm releasing version 1.1. We need to add a new 1.2 version to that
JIRA project.

- Of course, I really don't like the modifications to changes.xml where
the lines are not wrapped and all <action> are on one line. It makes it
very difficult to read :-) It has also wrecked all my careful
indentations that I had set over the past 2 years on all the plugins I
was managing... :-(

Thanks
-Vincent



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


RE: [proposa;l] New download report (was RE: [proposal] New feature for the plugin plugin (was RE: Little glitches in rc2 release process))

Posted by di...@multitask.com.au.
"Vincent Massol" <vm...@pivolis.com> wrote on 02/05/2004 06:34:01 PM:

> 
> 
> > -----Original Message-----
> > From: dion_gillard@multitask.com.au
> [mailto:dion_gillard@multitask.com.au]
> > Sent: 02 May 2004 08:57
> > To: Maven Developers List
> > Subject: Re: [proposa;l] New download report (was RE: [proposal] New
> > feature for the plugin plugin (was RE: Little glitches in rc2 release
> > process))
> > 
> > "Vincent Massol" <vm...@pivolis.com> wrote on 01/05/2004 08:46:15
> PM:
> > 
> > > Correction: the plugin plugin is definitely not the best place as
> this
> > > download report is generic and would work for any type of project,
> not
> > > just plugins.
> > >
> > > Any idea where it would fit best in the existing plugin set? Does it
> > > require a new plugin?
> > 
> > Isn't this just another report from the POM? Based on that it should
> go
> > into the xdoc plugin and be one of the ${maven.xdoc.pomDocuments}.
> 
> you're right. It makes sense. Especially as I've found Jason had started
> a downloads.xml file some time back but it appears the effort was
> stopped. I'll continue it. However, for the best possible
> implementation, we need a distributionUrl. I could make it a property of
> the xdoc plugin or we could add it to the POM. I've sent a proposal to
> add it to the POM. Failing this, I'll add it as an xdoc property.

I think for 1.0, a property is our only choice. For 1.1 and 2.0 POM 
changes are a possibility.
--
dIon Gillard, Multitask Consulting


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


RE: [proposa;l] New download report (was RE: [proposal] New feature for the plugin plugin (was RE: Little glitches in rc2 release process))

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: dion_gillard@multitask.com.au
[mailto:dion_gillard@multitask.com.au]
> Sent: 02 May 2004 08:57
> To: Maven Developers List
> Subject: Re: [proposa;l] New download report (was RE: [proposal] New
> feature for the plugin plugin (was RE: Little glitches in rc2 release
> process))
> 
> "Vincent Massol" <vm...@pivolis.com> wrote on 01/05/2004 08:46:15
PM:
> 
> > Correction: the plugin plugin is definitely not the best place as
this
> > download report is generic and would work for any type of project,
not
> > just plugins.
> >
> > Any idea where it would fit best in the existing plugin set? Does it
> > require a new plugin?
> 
> Isn't this just another report from the POM? Based on that it should
go
> into the xdoc plugin and be one of the ${maven.xdoc.pomDocuments}.

you're right. It makes sense. Especially as I've found Jason had started
a downloads.xml file some time back but it appears the effort was
stopped. I'll continue it. However, for the best possible
implementation, we need a distributionUrl. I could make it a property of
the xdoc plugin or we could add it to the POM. I've sent a proposal to
add it to the POM. Failing this, I'll add it as an xdoc property.

Thanks
-Vincent



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


Re: [proposa;l] New download report (was RE: [proposal] New feature for the plugin plugin (was RE: Little glitches in rc2 release process))

Posted by di...@multitask.com.au.
"Vincent Massol" <vm...@pivolis.com> wrote on 01/05/2004 08:46:15 PM:

> Correction: the plugin plugin is definitely not the best place as this
> download report is generic and would work for any type of project, not
> just plugins. 
> 
> Any idea where it would fit best in the existing plugin set? Does it
> require a new plugin?

Isn't this just another report from the POM? Based on that it should go 
into the xdoc plugin and be one of the ${maven.xdoc.pomDocuments}.
--
dIon Gillard, Multitask Consulting


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


[proposa;l] New download report (was RE: [proposal] New feature for the plugin plugin (was RE: Little glitches in rc2 release process))

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: 01 May 2004 12:38
> To: 'Maven Developers List'
> Subject: [proposal] New feature for the plugin plugin (was RE: Little
> glitches in rc2 release process)
> 
> 
> 
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > Sent: 01 May 2004 12:25
> > To: 'Maven Developers List'
> > Subject: Little glitches in rc2 release process
> >
> 
> [snip]
> 
> > - It's missing the download link for the new version in
> navigation.xml.
> > For example, for the 1.1 release of aspectwerkz plugin:
> 
> [snip]
> 
> Thinking about it, the best is probably to generate a download report
in
> one of the existing plugin. The report would consist of a page listing
> all available jar downloads for this plugin. It could be implemented
as
> follows:
> 
> - get all versions from <version> information in the POM
> - construct URLs:
> ${maven.remote.repo}/${pom.groupId}/${pom.artifactId}-${version}.jar
> - try connecting to the URL using <ant:get>. If it succeeds, put a
logo
> of a little green checkbox in a column of the report. If not, put a
red
> cross, meaning that download is not available.
> 
> The best place I have found to host this new report is within the
plugin
> plugin as it the one used to download/install plugins, to deploy
> plugins, etc.

Correction: the plugin plugin is definitely not the best place as this
download report is generic and would work for any type of project, not
just plugins. 

Any idea where it would fit best in the existing plugin set? Does it
require a new plugin?

Thanks
-Vincent



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


[proposal] New feature for the plugin plugin (was RE: Little glitches in rc2 release process)

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: 01 May 2004 12:25
> To: 'Maven Developers List'
> Subject: Little glitches in rc2 release process
> 

[snip]

> - It's missing the download link for the new version in
navigation.xml.
> For example, for the 1.1 release of aspectwerkz plugin:

[snip]

Thinking about it, the best is probably to generate a download report in
one of the existing plugin. The report would consist of a page listing
all available jar downloads for this plugin. It could be implemented as
follows:

- get all versions from <version> information in the POM
- construct URLs:
${maven.remote.repo}/${pom.groupId}/${pom.artifactId}-${version}.jar
- try connecting to the URL using <ant:get>. If it succeeds, put a logo
of a little green checkbox in a column of the report. If not, put a red
cross, meaning that download is not available.

The best place I have found to host this new report is within the plugin
plugin as it the one used to download/install plugins, to deploy
plugins, etc.

What do you think?

I'm happy to implement this if we're in agreement.
 
-Vincent



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