AFAIK, maven makes sure that it has all the plugins even before sorting the projects. It can not distinguish the fact that a subset of the projects do not need the plugin. Ideally maven should distinguish between a maven plugin and other plugins. If m2 snapshots are published somewhere, it will get an older copy of the plugins and happily continue the build.
Thanks Anita --- David Jencks <[EMAIL PROTECTED]> wrote: > > On Jun 25, 2006, at 4:06 AM, Jacek Laskowski wrote: > > > On 6/13/06, David Jencks <[EMAIL PROTECTED]> wrote: > >> Last (and only, depending on how you count) +1 was 4 days ago, any > >> chance 2 more people are willing to review this? > > > > I can't seem to test it out on my laptop with no Geronimo m2 builds > > done before. See > > http://issues.apache.org/jira/browse/GERONIMO-1738#action_12417669 > for > > more information. > > Something is odd, you should be able to build all the modules before > > any plugins. Have you run mvn -N install in geronimo's root > directory? > > I'd expect this to work: > > cd /cygdrive/c/oss/geronimo > mvn -N install > cd modules > mvn clean install > cd ../m2-plugins > mvn clean install > > I haven't tried this myself yet with a fresh repo.... will try to > find some time for this. > > > > > > Therefore, I can't vote for it. Does it mean I should vote against > it > > in such a case? > > > > I think we should investigate the problems further before voting > further. > > thanks > david jencks > > > >> david jencks > > > > Jacek > > > > -- > > Jacek Laskowski > > http://www.laskowski.net.pl > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
