I thought the biggest problem was that not all of our dependencies had
valid POMs, or at least not all their transitive dependencies had
valid POMs, so any Geronimo build eventually ran into missing/invalid
POMs and crapped out. There was a Wiki page where progress on this
front was being tracked. Anyone know where that issue stands?
Thanks,
Aaron
On 2/14/06, Anders Hessellund Jensen <[EMAIL PROTECTED]> wrote:
> I have submitted a patch migrating some of the simpler modules to Maven
> 2. The m2 build runs parallel with the m1 build. Nothing has been
> touched except POM files.
>
> http://issues.apache.org/jira/browse/GERONIMO-1624
>
> I suggest we continue along that path, making the m2 build run parallel
> with the m1 build. When the m2 build works, we can end the m1 build and
> change the directory layout to the new m2 layout, which should be very
> easy when we have a working m2 build.
>
> I've added POMs for activation, kernel, common, converter, core, util,
> system, deployment, management, derby, j2ee, j2ee-schema.
>
> Of course there may be errors in the build process of those modules, but
> they will probably surface when more modules are migrated to m2.
>
