Hi Ant, thanks for your answers, sorry for all these questions but it's my/our first time for publishing artifacts on a public maven repository ...
> ASF projects can get their artifacts published in the central Maven > repository (eg http://repo2.maven.org/maven2/) by copying them to > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ which I've just tried but it tells me "not available", is it caused by the down of people.apache.org of last days ? > automatically syncs with the central repo. To do that on > people.apache.org copy them to > /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository. All > committers should have access to do that. Todd, you are our man for publishing to people.apache.org (and related things), can you do it, or can you tell me how to do (many thanks) ? For the names, we have -incubator and release in file names, so this is already ok (i hope). For the folder, an org/apache/pivot is it right, or should be use something like org/apache/pivot-incubator ? >From what you tell me, i think it's better to wait after our upcoming 1.3 release has been released. Or in the mean time should we put also these versions of jars in another directory, because they need to be voted ? Or can we try to do all this stuff with out current 1.2 release (but without modifying jars) ? > Each artifact MUST have been voted on by a PMC and comply with all the > release requirements like having LICENSE, NOTICE, DISCLAIMER files, be > signed, and indicate they're incubating artifacts in the name eg by > including the "-incubating" suffix in the artifact name. A common way > of getting that vote done is by including the artifacts to be > published in a staging area which is pointed to in the release VOTE. But I've tried to look inside some of jars published under org/apache/... , and the aren't signed (or signed in this case means have sha1 files ?) and some doesn't contains LICENSE, NOTICE, DISCLAIMER files under a META-INF folder ... is it right ? So the real question: currently our jars doesn't have those files inside, so would it be better to have ? One last thing: the related pom file, we have to make it and publish, right ? But so do you think it's better to put also pom files inside the sources of the release ? Sorry for so many questions ... Thanks a lot, Sandro
