On Aug 22, 2011, at 7:06 PM, Vincent Massol wrote: > > On Aug 15, 2011, at 4:22 PM, Vincent Massol wrote: > >> Hi devs, >> >> We've had a meeting with Marius, Thomas and myself and we brainstormed about >> what to improve in our builds and we've come up with the following actions: >> >> 1- create twitter account for xwiki.org and tweet about releases (basically >> tweet links to blog posts). Category: Release Process improvement. Who: >> Vincent Massol >> 2- Refactor distribution for installers to share more. Who: Thomas Mortagne >> 3- Check latest version of izpack. Who: Marius >> 4- Configure nexus to cache other repos → speed improvement. Who: Vincent >> Massol >> 5- Add definition xwiki remote repo to top level repos in github. Who: >> Vincent Massol >> 6- Define a location for passwords. Who: Thomas Mortagne >> 7- Publish with commons and rendering on central repo. Who: ? > > Status update: We now have repos for XWiki on the sonatype infra: > > " > Configuration has been prepared, now you can: > * Deploy snapshot artifacts into repository > https://oss.sonatype.org/content/repositories/snapshots > * Deploy release artifacts into the staging repository > https://oss.sonatype.org/service/local/staging/deploy/maven2 > * Promote staged artifacts into repository 'Releases' > * Download snapshot and release artifacts from group > https://oss.sonatype.org/content/groups/public > * Download snapshot, release and staged artifacts from staging group > https://oss.sonatype.org/content/groups/staging > " > > The next step I'd like to do is find a way to push our 3.2M2 artifacts (for > commons and rendering) from our remote repo to the sonatype staging (for > promotion to central).
New status udate: * I've now staged commons and rendering 3.2M2: https://oss.sonatype.org/content/repositories/orgxwiki-038/ * The next step is normally for me to push the "release" action on the staged repo and it'll make it to central. * However, I've had to modify the top level pom since it was missing 2 pieces of information: <developers> and <description>, which means what I've staged is not really a 3.2M2 release (it is except for the top level pom). As a consequence I won't release the staged repo. * We're now ready to push the next release (3.2M3) to Maven Central when we release it. * FTR here are the steps I've followed to build and stage the artifacts: - Add the following in your settings.xml: <server> <id>sonatype-nexus-staging</id> <username>userid</username> <password>password</password> </server> - Add passphrase in settings.xml or pass it on command line using -Dgpg.passphrase=… <properties> <gpg.passphrase>password</gpg.passphrase> </properties> - in xwiki-commons and in xwiki-rendering, after having checked out the correct tag, run: mvn clean deploy -Prelease -DaltDeploymentRepository=sonatype-nexus-staging::default::https://oss.sonatype.org/service/local/staging/deploy/maven2 Thanks -Vincent > Thanks > -Vincent > >> >> I've started to work on items 4 and 5 and will do 1 soon. >> >> Also I've analyzed 7 and there's only 1 external reps not available in the >> Maven Central Repo: >> <groupId>org.reflections</groupId> >> <artifactId>reflections</artifactId> >> >> It should be pretty easy to submit it using >> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central >> To publish our artifacts to the central repo I propose to use Sonatype OSS >> service, see >> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide >> >> Thanks >> -Vincent >> > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
