Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=JVHxDow5KGTKqRDpkhg8yOtg6GV4xgWCiqZ5KG8krcM0GymbHN4ynSS9nYjKebK2yUZrZgxqjBJPJH8VUQ0FjhvZdKTQI2k5Yj/FzXVDf0aoBb1D/DEZZf2W/bwKejtSvE272D6aMN9dmpDlQg1ycY+RQZf+wI62htu5tLulZV0=
Message-ID: <31cc37360603091206h3d24fa6dn2064dd4796c90fc4@mail.gmail.com>
Date: Thu, 9 Mar 2006 12:06:29 -0800
From: "Henri Yandell" <flamefew@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: M2 migration status
In-Reply-To: <31cc37360603091040u1e595c41ie1b1fbf7dc4a210@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1b5bfeb50603080337t3827348dn@mail.gmail.com>
	 <31cc37360603081150p7b36d9e0rbaf2195d46bb415a@mail.gmail.com>
	 <1b5bfeb50603090453o724f704bn@mail.gmail.com>
	 <c278ac970603090741j4701baf3k45a126c83453fe39@mail.gmail.com>
	 <44105663.70807@earthlink.net>
	 <31cc37360603091040u1e595c41ie1b1fbf7dc4a210@mail.gmail.com>

On 3/9/06, Henri Yandell <flamefew@gmail.com> wrote:
> On 3/9/06, Joe Bohn <joe.bohn@earthlink.net> wrote:
> >
> > Prasad Kashyap wrote:
> >
> > > Here's my next concern. For these modules that have migrated to m2, w=
e
> > > should include them in the daily G builds as soon as possible. If we
> > > don't pull out the m1 build artifacts, project.xml and maven.xml from
> > > the migrated modules, then there's a chance that those may get change=
d
> > > behind our backs while we go forward converting more. There might be =
a
> > > regression of issues.
> >
> > I have the same concern and voiced it (from the other direction) in my
> > post on little-G.
>
> Ditto, so I now start my day by running a build-fresh-geronimo script. :)

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.

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 :)

Hen