We are now able to deploy binary artifacts to the Apache nexus instance. Yay! I tried deploying locally and it works. Also configured the auto-deploy in Travis CI, but need to test it.
Configuration has been prepared, now we can: * Deploy snapshot artifacts into repository https://repository.apache.org/content/repositories/snapshots/org/apache/samoa/ (already deployed the first snapshot from master) * Deploy release artifacts into the staging repository https://repository.apache.org/service/local/staging/deploy/maven2 (login required, it is linked to your Apache id) * Promote staged artifacts into repository 'Releases' * Download snapshot and release artifacts from group https://repository.apache.org/content/groups/public * Download snapshot, release and staged artifacts from staging group https://repository.apache.org/content/groups/staging -- Gianmarco On 29 June 2015 at 14:15, Gianmarco De Francisci Morales <[email protected]> wrote: > A bit late, but we are almost ready for the first Apache release. > > I am waiting for INFRA to configure the Nexus repository for the artifacts. > In the meanwhile, I fixed all the files needed for the release (or at > least, I hope so, SAMOA-37 > <https://issues.apache.org/jira/browse/SAMOA-37>). > > There are two outstanding PRs that need to be merged before the release, > SAMOA-34 and SAMOA-36. If somebody can have a look at them it would be > great. > In the meanwhile, I managed to prepare the release artifacts (the source > distribution). > It seems we have some problem with the maven javadoc plugin (seems > something related to MJAVADOC-398 > <https://issues.apache.org/jira/browse/MJAVADOC-398>). It craps out > without finding the right dependencies. > I have disabled the automatic creation of the Javadoc for the release, as > we have to publish it manually on the website anyway. > > I'll post the RC and a VOTE thread as soon as the PRs are in and I have > tested the deployment of the artifacts. > > Cheers, > -- > Gianmarco >
