I made this change in trunk yesterday in r673459, will merge it to the 1.3 branch today if no problems are reported with the change in trunk.
...ant On Tue, Jul 1, 2008 at 9:47 AM, Simon Laws <[EMAIL PROTECTED]> wrote: > > > On Tue, Jul 1, 2008 at 7:48 AM, ant elder <[EMAIL PROTECTED]> wrote: > >> Yes trunk is now on version 3-SNAPSHOT but the 1.3 branch is still on >> 2-incubating isn't it? We'd need to do an official release of the new one to >> use it with the 1.3 release so I'd vote for just dropping the parent pom >> now. >> >> ...ant >> >> >> On Mon, Jun 30, 2008 at 4:15 PM, Simon Laws <[EMAIL PROTECTED]> >> wrote: >> >>> >>> >>> On Mon, Jun 30, 2008 at 3:06 PM, ant elder <[EMAIL PROTECTED]> wrote: >>> >>>> On Mon, Jun 23, 2008 at 10:41 PM, Raymond Feng <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>> > Hi, >>>> > >>>> > Now Tuscany is a TLP. We have to make a few changes in the parent pom >>>> [1], >>>> > such as: >>>> > >>>> > 1) Remove incubating from the version numbers (including the >>>> java/pom.xml >>>> > [2]). >>>> > 2) Change <distributionManagement> section so that >>>> > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ will be >>>> used >>>> > for mvn:deploy. >>>> > 3) Change the<url> for tuscany to use http://tuscany.apache.org. (I >>>> did >>>> > these already). >>>> > >>>> > I think we should do the above for 1.3 release branch too. Please feel >>>> free >>>> > to add anything that I might have missed. >>>> > >>>> > Thanks, >>>> > Raymond >>>> > >>>> > [1] http://svn.apache.org/repos/asf/tuscany/java/pom/parent/pom.xml >>>> > [2] https://svn.apache.org/repos/asf/tuscany/java/pom.xml >>>> > >>>> >>>> Whats the status of this? I might be coming in a little late but how >>>> about >>>> just dropping the tuscany parent pom altogether? We discussed this >>>> recently >>>> and have done it for the SDO 1.1.1 release - >>>> http://apache.markmail.org/message/dq2btsacsawfznop >>>> >>>> ...ant >>>> >>> >>> The 1.3 branch now uses the new parent pom as does the trunk I believe. >>> >>> I've no objection to moving away from the parent pom but I think we >>> should come to some conclusions about our distribution story first just in >>> case we need it. >>> >>> Simon >>> >> >> > I have the 1.3 pom change sitting on my disc waiting to go. > > I though I had started a VOTE on this last week but of course that mail > when the way of most of the things I sent toward the end of last week. > > So, if you're happy to make the pom changes, I 'll go along with removing > it and worry about our distribution story separately. > > Simon >
