maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maczka Michal <>
Subject RE: idea: collector+executor vs reactor
Date Thu, 21 Oct 2004 07:57:02 GMT

> -----Original Message-----
> From: Jason van Zyl []
> Sent: Wednesday, October 20, 2004 5:58 PM
> To: Maven 2 Developers List
> Subject: idea: collector+executor vs reactor
> Howdy,
> This may result in nothing but I just tried to do a 
> m2 -r pom:install 
> In continuum just to get the POMs all installed but of course m2 went
> through it's inheritance song/dance and can't install the POMs because
> the POMs aren't installed :-)
> So I was thinking that you might just want to collect the POMs and
> execute some goal. At least for installing or deploying POMs 
> this might
> be useful. 
>Just a thought. With the unified source directory this
> problem would go away but maybe there are other uses.

There is few more point which are not clear for me:

a) Will we have sort of master project - which are defing which subproject
it will process?
b) Will the list of pom which is built by reactor be passed to plugins?
c) Will the single goal be responsible for both modes of processing? 
   I mean something analogous to "maven site"  versus "maven

I think we need a) and b) in order to have a possibility of aggregating
results. E.g. for making websites, creating idea projects with modules etc.

It would be nice to use special type for marking project as "master" . Maybe
someting like:

   <type>multiproject</type>  or <type>master</type>

This will have bring some magic - when I will type:

m2 site - it will generate aggregated site
m2 install - it will call install on all subproject

So the idea is that there will be always one goal like site, install which
will have different effects depeding on situtational context.


View raw message