On Wed, Jul 14, 2010 at 10:26 AM, Mike Edwards <[email protected]> wrote: > ant elder wrote: > <snip> >> >> Thats great, i'll go look at updating 2.x to use that. >> >> Echoing Raymonds comment, it would be good to get it into the central >> repo. >> >> Any chance the compliance test artifacts could also get added to the repo >> too? >> >> ...ant >> > Ant, Raymond, > > You have both suggested that it would be good to publish the OASIS artifacts > to the central Maven repo. > > Can you explain to me why this is desirable? Why is the current OASIS > location not adequate? > > I would also appreciate some instruction on what it will take to publish > these artifacts into the central Maven repo, please. >
It sounds like the Maven people want to make the central repo only contain artifacts where all the dependencies are themselves contained in the central repo. So its possible at some point it will start making it difficult to get Tuscany releases put into the central repo if it uses dependencies that aren't also in the central repo. That doesn't sound imminent though so the current OASIS location _is_ adequate for now. See these emails for some comments: http://apache.markmail.org/message/bn47mylhmj5x2qcq http://apache.markmail.org/message/l4qjyi6zuiexv46u http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/ I've only ever done it at Apache which uses the auto rsync mechanism so i've not had to go through the external Maven process, all i can do is point you to the maven guide - http://maven.apache.org/guides/mini/guide-central-repository-upload.html ...ant (I'll reply separately about the test artifacts)
