> All the plugins are in ../maven-plugins and the location > specified is control in the project.properties in the core > Maven build.
I know - I'm trying to find out where Jorg has something screwy because it works for everyone else. > > > You are only attempting to build with these plugins: > > [exec] Maven Eclipse Plug-in > > [exec] Maven Genapp Plugin > > [exec] Maven JBuilder Plug-in > > [exec] Maven WAR Plugin > > What is this supposed to signify? These are the only plugins he is attempting to build, meaning maven-plugins is incomplete or build/project.properties is excluding the rest. > > > Looks like moving the bootstrap-required plugins out of the > core was > > not such a great idea... > > Sure it was, doesn't matter where they are. I think these are > the expected road bumps in moving them as they need to be > separated and is the only way we'll flush out all the little > quirks in the build. Except that there are two setup steps now instead of one. What if the bootstrap were to checkout from CVS the required plugins to build itself, then build the rest from the given location (including rebuilding the core)? Although that would be a pain offline. Are we expecting a maven source distribution to require a binary distribution to build itself, or do we make them download 2 distros (core and plugins) + ant? Cheers, Brett
