Looks good Mauro. Thanks.
My only comment is about the "category" addition to a dependency. Can you
explain the usage of this with an example? My impression was that the form
of copying out of the "jars" directory should not be done, and instead use
${dependency.path}, to allow for jar overrides.
Cheers,
Brett
> -----Original Message-----
> From: Mauro Talevi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 21 October 2003 6:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: maven-release
>
>
> Brett Porter wrote:
>
> >
> > This sounds about right. I'd had plans to do some such
> thing, as for
> > our workplace I created an installer plugin that basically
> does bits
> > of dist and a bit more to create a tarball. Also, the SCM
> plugin has
> > release type stuff in there that overlaps some with the release
> > plugin. Rationalising all of this into dist +
> release-on-top-of-dist
> > is a great thing.
>
> I'm attaching a first patch incorporating the scm plugin.
> In this approach all distros would be built off scm.
> (requires maven.scm properties to be set in the project
> running the plugin - that needs to be documented) This also
> leads to a much simplified structure for the src and bin
> archive/assembly dirs (effectively I'm not using those).
>
> > I'm happy to send you the installer plugin offline to add
> that content
> > if you are working on this.
>
> I still have to look at it :-)
>
> Anyway, do let me know if you like the direction taken so far.
>
> Cheers, Mauro
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
