geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap" <goyathlay.geron...@gmail.com>
Subject Re: M2 migration status
Date Fri, 17 Mar 2006 14:55:51 GMT
All but just the following 4 modules to be migrated.

interop
jetty
jetty-builder
axis-builder.

Then there are the "almost-there" modules. These modules have pending
work like one of the following -
1. tests don't work due to surefire plugin's bugs
2. properties/other resources are not procesed.
3. properties/resources are not in the m2 dir structure.

Patches ready :
j2ee-builder : http://issues.apache.org/jira/browse/GERONIMO-1713
axis-builder : http://issues.apache.org/jira/browse/GERONIMO-1723

Cheers
Prasad

On 3/13/06, Prasad Kashyap <goyathlay.geronimo@gmail.com> wrote:
> j2ee-builder done. I have also pruned the dependency lists for
> j2ee-builder and j2ee.
>
> Will update the patch now.
>
> Cheers
> Prasad
>
> On 3/13/06, Henri Yandell <flamefew@gmail.com> wrote:
> > On 3/10/06, Jacek Laskowski <eljotpl@gmail.com> wrote:
> > > 2006/3/9, Henri Yandell <flamefew@gmail.com>:
> > >
> > > > The geronimo-spec-j2ee-deployment module was giving errors; but I
> > > > realised I was building under JDK 1.5. It works fine under 1.4; so
> > > > something for the future there perhaps.
> > >
> > > I think I've seen a way to make sure that M2 is used on Java 1.4.
> > >
> > > Now, there might be a way to leverage it and ensure Java 1.4 runtime.
> > >
> > > > Next I get errors from the Geronimo :: Directory module; this is
> > > > because I'm being a aggressive and turning off the snapshot
> > > > repositories in the top pom. directory-asn1 depends on commons-test,
> > > > which is unreleased. In this case the ideal solution is to set
> > > > commons-test to test scope so it doesn't end up in the build - I'll
> > > > work on getting that changed - or just having them not depend on
> > > > commons-test :)
> > >
> > > Great. I'm looking forward to committing your patch ;)
> >
> > Fixed it at the other end. The commons-test dependency no longer gets
> > passed along transitively.
> >
> > Now I find that everything builds from the top down - except for the 2
> > Tomcat tests that already appear to be being looked into. This is with
> > the snapshot repositories commented out - they slow things down and
> > seem to lead to errors that mean I have to keep repeating the build
> > until they've finally downloaded things. There's some way to change
> > their strategy I think - must look into this.
> >
> > Slowly moving axis-builder along. Looks like the Maven xmlbeans plugin
> > depends on a snapshot version of xmlbeans, so that's irritating :)
> >
> > Hen
> >
>

Mime
View raw message