> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: dimanche 5 juin 2005 23:39
> To: Maven Developers List
> Subject: Re: latest plugin releases on the maven download page
> 
> This page is quite different. It lists out what the 1.0.2 versions were,
> and only lists plugins that have changed. AFAIK, the multichanges plugin
> doesn't do that. 

No, it doesn't do this. But it's close and could be changed to do this.

It displays the latest release for each plugin as shown on
http://people.apache.org/~vmassol/multichanges.jpg

> I've never used it to be honest, I always assumed it
> aggregated changes.xml files (which means actual changes, not just
> listing versions) - and the one line of documentation on the site
> indicates that as well.

I guess it's a bit a misnomer. It doesn't aggregate changes.xml. The reason
it's called multichanges is because it uses the changes.xml files to gather
the release information. But I agree the name is not the best possible...
 
> Is it really suitable for the task? If so, please go ahead and add it
> back.

On a slightly OT:

I think we should do the following:

- Have a CI for the Maven plugins web site so that it is published every few
hours
- If the site build fails, an email is sent to the maven dev mailing list
with the error
- Make sure the multichanges plugin gets built as part of the plugins site
(I've checked and it is actually still there in the report list, so it's
just a matter or running the site build)
- Improve the multichanges plugin to add a RSS feed.
- Advertise it

This will allow people to get a fresh list of the latest version of plugins.
This will allow them to get RSS notifications as soon as a new plugin is
released (and I'll stop what I've started on mavenbook.org, i.e. announcing
plugin releases).

WDYT?

I don't have much time right now but I guess I could do the multichanges
modification to add the generation of a RSS feed. If someone could do the
5-10 lines shell script to build the plugins site that would be great (or
use CC or something else).

-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to