Return-Path: Delivered-To: apmail-incubator-aries-dev-archive@minotaur.apache.org Received: (qmail 24376 invoked from network); 25 Mar 2010 17:06:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Mar 2010 17:06:57 -0000 Received: (qmail 6167 invoked by uid 500); 25 Mar 2010 17:06:57 -0000 Delivered-To: apmail-incubator-aries-dev-archive@incubator.apache.org Received: (qmail 6056 invoked by uid 500); 25 Mar 2010 17:06:57 -0000 Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: aries-dev@incubator.apache.org Delivered-To: mailing list aries-dev@incubator.apache.org Received: (qmail 6048 invoked by uid 99); 25 Mar 2010 17:06:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 17:06:57 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jpjhughes@gmail.com designates 209.85.220.212 as permitted sender) Received: from [209.85.220.212] (HELO mail-fx0-f212.google.com) (209.85.220.212) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 17:06:51 +0000 Received: by fxm4 with SMTP id 4so4219351fxm.20 for ; Thu, 25 Mar 2010 10:06:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to :content-type:content-transfer-encoding; bh=4zVjvq9FGOjlbi/C7v38qWisnkfBOe8dnhoNIy8sq6w=; b=ag2QfOlB03ZzgLeB1NVVdQyFJkBJHYSxpMkmL5wiVbHyvOBRZbFfvcoIJ15pU6Oy+h /Q4Wi2xZ3jRHMbmdjS01db75Z0fAwbK6aZH8SAgoPUcJjMPK+g0gkrriwrVe1WIKLRUJ YFRddQrNobA6aya9Tle9BseInavHaUfC71GJk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=D5J85GYreGcWevVzubawrRfCzBDmzJhQMRDsgatSZKOcc0R+6/GpKrPy7CK8WxBoNk RWC5UNYhgnaecgpqXgF/wpEiYg6obQA8XwOfGEB/bPRp1QqOZiHwajaCEGo3gUvixhFu lXZGg7OGiPnMRVqyOElf89435CIAI/jnMob44= MIME-Version: 1.0 Sender: jpjhughes@gmail.com Received: by 10.223.64.84 with SMTP id d20mr17357fai.76.1269536790508; Thu, 25 Mar 2010 10:06:30 -0700 (PDT) In-Reply-To: References: <089AD5C1-41BC-4D16-9A0C-A75665935F77@toolazydogs.com> From: Jeremy Hughes Date: Thu, 25 Mar 2010 17:06:10 +0000 X-Google-Sender-Auth: f558e887429450ac Message-ID: Subject: Re: Build failure To: aries-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 25 March 2010 06:34, Guillaume Nodet wrote: > The problem will be when the release is actually created. > Usually, the release is done using the maven release plugin and the > following command: > =A0 mvn release:prepare release:perform > This will fail because the plugin won't be available in the build just af= ter > it upgraded the version to the non snaphshot one for the release. > > Even from a practical point of view, i think it will be easier if we have= to > do "mvn release:prepare release:perform" multiple times, rather than havi= ng > to work around this tooling and do the release ourselves. > THe only drawback is that it leads to multiple tags, but this also mean t= hat > =A0we'll later be able to release the components separatly. If the only drawback is that it clutters up the 'tags' / 'releases' dir then I think that's manageable. > > The other option, as Lin says, is to move the plugin out of the main trun= k > and have multiple (at least two) trunks. > > On Thu, Mar 25, 2010 at 07:15, Alasdair Nottingham wrote= : > >> Once the release is done and the artifacts are in a maven repo you will = be >> able to do mvn clean install. It fails now because there is no >> eba-maven-plugin in a maven repo. >> >> Alasdair >> >> >> On 25 Mar 2010, at 01:43, Lin Sun wrote: >> >> =A0I'd think a required test before every single release is that user >>> should be able to build the source tree using "mvn clean install" with >>> a clean local .m2 repo. =A0I am concerned that not releasing the eba >>> maven plugin first will fail that test. >>> >>> Lin >>> >>> On Wed, Mar 24, 2010 at 4:36 PM, Alasdair Nottingham >>> wrote: >>> >>>> It sounds like we are quite close to having the release ready so >>>> perhaps we can release everything at the same time right now, and more >>>> to a separate release model for subsequent releases? >>>> >>>> Alasdair >>>> >>>> On 24 March 2010 20:21, Lin Sun wrote: >>>> >>>>> Right, I mean the eba maven plugin and its dependency out of the >>>>> current trunk dir, unless we get rid of its current parent pom >>>>> dependency. >>>>> >>>>> That way, we can have 2 releases, 2 votes and 2 tags, which is less >>>>> overhead than each subproject has its own tag. =A0And if the eba plug= in >>>>> is stable, in a future release, we just need to do 1 release, 1 vote >>>>> and 1 tag of aries trunk. >>>>> >>>>> Lin >>>>> >>>>> On Wed, Mar 24, 2010 at 3:00 PM, Guillaume Nodet >>>>> wrote: >>>>> >>>>>> I don't think that would work, because the the eba maven plugin depe= nds >>>>>> at >>>>>> least on the parent poms, so we would need at least a release for >>>>>> those. >>>>>> I don't see any real problems in having each subproject associated w= ith >>>>>> its >>>>>> own tag personally, but it's a bit more overhead when releasing the >>>>>> whole >>>>>> thing. >>>>>> >>>>>> On Wed, Mar 24, 2010 at 20:54, Lin Sun wrote: >>>>>> >>>>>> =A0I was trying to suggest things in a soft way :-) =A0I agree that = we >>>>>>> should release the eba plugin first. >>>>>>> >>>>>>> We could release the eba plugin first with a tag (after we move it = out >>>>>>> of the trunk dir), then release the other subprojects together with >>>>>>> another tag. >>>>>>> >>>>>>> Lin >>>>>>> >>>>>>> >>>>>>> On Wed, Mar 24, 2010 at 2:28 PM, Guillaume Nodet >>>>>>> wrote: >>>>>>> >>>>>>>> The problem isn't that it makes sense or not, it's that in order t= o >>>>>>>> >>>>>>> release >>>>>>> >>>>>>>> aries, we'll have to have the aries plugin released before hand. = =A0So >>>>>>>> >>>>>>> we'll >>>>>>> >>>>>>>> have to release all the subprojects separatly (even if we do that >>>>>>>> under a >>>>>>>> single vote / staging repo and whatever else), but this means we'l= l >>>>>>>> have >>>>>>>> multiple tags. >>>>>>>> >>>>>>>> On Wed, Mar 24, 2010 at 19:58, Lin Sun wrot= e: >>>>>>>> >>>>>>>> =A0Patch looks good, assuming you can build eba-maven-plugin using= the >>>>>>>>> init profile successfully. >>>>>>>>> >>>>>>>>> Does it make sense for us to release the eba-maven-plugin >>>>>>>>> separately, >>>>>>>>> so that user doesn't have to build aries using the init profile >>>>>>>>> first? >>>>>>>>> >>>>>>>>> Lin >>>>>>>>> >>>>>>>>> On Wed, Mar 24, 2010 at 1:40 PM, Alan D. Cabrera < >>>>>>>>> list@toolazydogs.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I did attach a file. >>>>>>>>>> >>>>>>>>>> Index: pom.xml >>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>>> --- pom.xml =A0 =A0 (revision 927124) >>>>>>>>>> +++ pom.xml =A0 =A0 (working copy) >>>>>>>>>> @@ -38,18 +38,6 @@ >>>>>>>>>> >>>>>>>>>> =A0 >>>>>>>>>> =A0 =A0 =A0 parent >>>>>>>>>> - =A0 =A0 =A0 =A0eba-maven-plugin >>>>>>>>>> - =A0 =A0 =A0 =A0testsupport >>>>>>>>>> - =A0 =A0 =A0 =A0util >>>>>>>>>> - =A0 =A0 =A0 =A0blueprint >>>>>>>>>> - =A0 =A0 =A0 =A0jndi >>>>>>>>>> - =A0 =A0 =A0 =A0transaction >>>>>>>>>> - =A0 =A0 =A0 =A0web >>>>>>>>>> - =A0 =A0 =A0 =A0application >>>>>>>>>> - =A0 =A0 =A0 =A0jmx >>>>>>>>>> - =A0 =A0 =A0 =A0jpa >>>>>>>>>> - =A0 =A0 =A0 =A0spi-fly >>>>>>>>>> - =A0 =A0 =A0 =A0samples >>>>>>>>>> =A0 >>>>>>>>>> >>>>>>>>>> =A0 >>>>>>>>>> @@ -63,4 +51,37 @@ >>>>>>>>>> =A0 =A0 =A0 >>>>>>>>>> =A0 >>>>>>>>>> >>>>>>>>>> + >>>>>>>>>> + =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0default >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0true >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0testsupport >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0util >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0blueprint >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jndi >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0transaction >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0web >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0application >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jmx >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jpa >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0spi-fly >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0samples >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 >>>>>>>>>> + >>>>>>>>>> + =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0init >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0false >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0eba-maven-plugin >>>>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 >>>>>>>>>> + =A0 =A0 =A0 =A0 >>>>>>>>>> + >>>>>>>>>> + =A0 =A0 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mar 24, 2010, at 11:04 AM, Lin Sun wrote: >>>>>>>>>> >>>>>>>>>> =A0I think using profiles is fine or perhaps we can move the >>>>>>>>>>> eba-maven-plugin to its own tree/build and release the >>>>>>>>>>> eba-maven-plugin separately (which seems reasonable). >>>>>>>>>>> >>>>>>>>>>> P.S. did you intend to attach a file? =A0anyway I don't see it. >>>>>>>>>>> >>>>>>>>>>> Lin >>>>>>>>>>> >>>>>>>>>>> On Wed, Mar 24, 2010 at 12:55 PM, Alan D. Cabrera < >>>>>>>>>>> >>>>>>>>>> list@toolazydogs.com >>>>>>> >>>>>>>> >>>>>>>>>> =A0wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Here's a possible fix using profiles. =A0WDYT? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Alan >>>>>>>>>>>> >>>>>>>>>>>> On Mar 24, 2010, at 10:45 AM, Lin Sun wrote: >>>>>>>>>>>> >>>>>>>>>>>> =A0Hi >>>>>>>>>>>>> >>>>>>>>>>>>> I think I ran into similar issues yesterday when I tried to >>>>>>>>>>>>> build >>>>>>>>>>>>> >>>>>>>>>>>> with >>>>>>> >>>>>>>> a clean .m2 repo. =A0I remember I had to manually build the >>>>>>>>>>>>> default-parent, parent, then eba-plugin to get around this. >>>>>>>>>>>>> We'll >>>>>>>>>>>>> have to make sure we can build aries with a clean .m2 repo >>>>>>>>>>>>> before >>>>>>>>>>>>> >>>>>>>>>>>> we >>>>>>> >>>>>>>> release. >>>>>>>>>>>>> >>>>>>>>>>>>> Lin >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Mar 24, 2010 at 12:39 PM, Alan D. Cabrera < >>>>>>>>>>>>> >>>>>>>>>>>> list@toolazydogs.com> >>>>>>>>> >>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'm on a new tower and I tried to do a fresh build and it fa= ils >>>>>>>>>>>>>> >>>>>>>>>>>>> because >>>>>>>>> >>>>>>>>>> of a >>>>>>>>>>>>>> missing EBA plugin. =A0I try to build the EBA plugin and it = fails >>>>>>>>>>>>>> >>>>>>>>>>>>> because >>>>>>>>> >>>>>>>>>> it's >>>>>>>>>>>>>> missing a parent. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Shouldn't we control this build process via profiles at the = SVN >>>>>>>>>>>>>> >>>>>>>>>>>>> root? >>>>>>> >>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> Alan >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Cheers, >>>>>>>> Guillaume Nodet >>>>>>>> ------------------------ >>>>>>>> Blog: http://gnodet.blogspot.com/ >>>>>>>> ------------------------ >>>>>>>> Open Source SOA >>>>>>>> http://fusesource.com >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> Guillaume Nodet >>>>>> ------------------------ >>>>>> Blog: http://gnodet.blogspot.com/ >>>>>> ------------------------ >>>>>> Open Source SOA >>>>>> http://fusesource.com >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Alasdair Nottingham >>>> not@apache.org >>>> >>>> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >