I pressed send too early on my last note. So now we have a version of the parent pom with the 2-incubator-SNAPSHOT version tag and a version of buildtools with the 1.0-incubator-SNAPSHOTavailable from the m2-snapshot-repository, meaning that you no longer need to do a source build on these projects to get the artifacts into your local repo. All of the Tuscany java projects depend on these artifacts.
We'll need to be aware that if we change anything in these projects we ought to update the snapshot repo. I have done a chmod 755 on the directory hierarchies in the repository so that other committers can make the updates if and when necessary. Regards, Kelvin. On 05/12/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Dec 5, 2006, at 1:38 AM, kelvin goodson wrote: > I had a little dig around and I'm tring to work out if the purpose > of the > people.apache.org m2-snapshot-repository is right for solving this > issue. > If we can post an incubator-SNAPSHOT version of buildtools and > parent pom > there, then I think that would solve this issue. +1 I think we should start publishing occasional snapshots of trunk projects to the snapshot repo so that most modules can be built separately. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
