Re: [Maven-plugins-developer] maven-deb-plugin is ready for 0.5 release

[Andy J. <an...@aj...>]

On Monday 22 Sep 2003 22:46, Trygve Laugst=F8l wrote:
> I've hacked up the plugin to be ready for a 0.5 release. It's still rather
> basic but I would like to get it out to be able to get some feedback and
> suggestions.

Good work

> I don't know how your routines are for releasing a plugin. What I would
> like to do is to update the pom and tag the /deb directory with a release
> tag.

What we normally do is
* update the site ("maven multiproject") and copy across to Sourceforge
* build your plugin ("maven plugin" in the directory of the plugin) and cop=
y=20
it across to Sourceforge.

> I don't know which version that is recomended for building the site and
> the artifact with when releasing, I'm currently using a rather fresh HEAD.

Version of Maven ? I use beta10 since it is the latest 'released' version -=
=20
but I do use the 1.0 release of the multiproject plugin since that is a=20
requirement.

> And I was wondering about a couple of other issues:
>
> I've noticed some errors in the plugin-project.xml and README file. Is it
> okay if I commit the changes or would some of the project admins like to
> take look at the changes as a patch?

I doubt that there are any 'errors' in these files :-). The README simply=20
provides a list of instructions/guidelines for the project. Do you mean you=
=20
want to add some more guidelines ? If so, then update the file.

As far as the plugin-project.xml goes, it is used by all of the plugins and=
 so=20
provides the default values of various things. If you want to specify=20
something different you put it in your plugins project.xml. What specifical=
ly=20
needs changing in that file ?

> And I would like to make a xdoc page listing the responsible persons for
> each of the plugins to make it easier to get in touch with the responsible
> persons of a plugin for both users and developers. Or perhaps have another
> role like Plugin Manager. Or both with the xdoc page beeing generated
> from the roles in the poms. Just a thought.. :)

Sounds like a good idea.
A couple of things I've wanted to do (but not had time yet) are
* Update the multiproject plugin to allow override of the template, so that=
 we=20
can update the "plugin overview" page. We can then have links to the goals=
=20
and properties pages of each plugin.



=2D-=20
Andy