On 27 February 2012 17:57, Mladen Turk <mt...@apache.org> wrote: > On 02/27/2012 06:14 PM, sebb wrote: >> >> Can you also release the jar to Maven please? > > > Sure, already did steps described at > http://commons.apache.org/releases/release.html > > files are already inside > /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon > and maven-metadata.xml updated. > > According to the release.html this should sync to repo1.maven.org > (if the instructions are valid of course)
They are out of date for Nexus-enabled components, which Daemon is. Not sure how you managed to update the directory; when a component uses Nexus, manual updates are supposed to be disabled. I see that the 1.0.9 jar is also present, but has not been propagated to Maven Central (as we know from the Clirr story). [Later] Just realised what the problem is - the files are installed under the directory which corresponds to the groupId org.apache.commons, but the pom actually has groupId commons-daemon. This is one of the pitfalls of the manual deployment method in the (outdated) release docs. I can probably fix that via Nexus. Note: we could change the groupId to o.a.c, but that would require a package name change as well otherwise classpath clashes could occur. > > > Regards > -- > ^TM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
