"Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/11/2003 07:54:55 PM:
> dIon,
>
> I don't quite agree. Each of these plugins are separate. Sharing the
> same properties ties them together. I would agree, provided the
> multiproject plugin provides some useful infrastructure for all plugins
> deal
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 11 November 2003 11:16
> To: Maven Developers List
> Subject: Re: cvs commit:
maven-plugins/multichanges/src/plugin-resources
> releases.jsl
>
> Vincent Massol wrote:
>
> >
Vincent Massol wrote:
dIon,
I don't quite agree. Each of these plugins are separate. Sharing the
same properties ties them together. I would agree, provided the
multiproject plugin provides some useful infrastructure for all plugins
dealing with several projects. In which case the other plugins w
2
> To: Maven Developers List
> Subject: Re: cvs commit:
maven-plugins/multichanges/src/plugin-resources
> releases.jsl
>
> Vincent,
>
> is there a reason that we're not using the multiproject plugin for
these,
> or at least the same property names?
&g
Vincent,
is there a reason that we're not using the multiproject plugin for these,
or at least the same property names?
We now have
maven.multichanges.basedir=${basedir}
maven.multichanges.includes=*/project.xml
maven.multichanges.excludes=**/target/**/project.xml,project.xml
maven.multichanges.
