Nice, looks very straight forward. If it's ok, I would like to hold on publishing our first java client release, 1.0.0, in favor of our next client release 1.1.0. Device data should be good to go for all our released versions.
Question... why duplicate the documentation locally for our project? Do you want the steps customized to match our project and build environment? Thanks!! <div>-------- Original message --------</div><div>From: Bertrand Delacretaz <[email protected]> </div><div>Date:09/05/2014 4:45 AM (GMT-05:00) </div><div>To: [email protected] </div><div>Subject: How to deploy artifacts to Maven Central </div><div> </div>Hi, IIRC there was a question about this a while ago - the info is at http://www.apache.org/dev/publishing-maven-artifacts.html I'm not sure if using the Apache parent pom is required for that, but if it is that's <parent> <groupId>org.apache</groupId> <artifactId>apache</artifactId> <version>14</version> </parent> and once again, it would be very nice if someone could document the release steps at http://incubator.apache.org/devicemap/ for future releases.http://sling.apache.org/documentation/development/release-management.html is a good example of that. HTH, -Bertrand
