commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Commons Wiki] Update of "ReleaseDeployment" by sebbapache
Date Tue, 11 Jun 2013 00:35:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.

The "ReleaseDeployment" page has been changed by sebbapache:
https://wiki.apache.org/commons/ReleaseDeployment?action=diff&rev1=5&rev2=6

  
  So the process would be:
   * mvn deploy -Ptest-deploy
-  * use some script to move the tarballs into their own directory structure
+  * use some script (e.g. Ant as part of commons-build plugin) to move the tarballs into
their own directory structure
-  * use scm-publish:publish-scm to publish the tarballs
+  * use scm-publish:publish-scm or svnmucc to publish the tarballs
-  * use Nexus Maven plugin to deploy & close the jars
+  * use Nexus Maven plugin to deploy & close the jars - the plugin does not seem to work.
See below.
  
  The script to move the tarballs could probably be written in Ant and invoked by Maven, e.g.
using a specific profile.
  
+ Nexus Maven plugin seems not to work and the docs have not been updated recently.
+ However, it is quite easy to use HTTP POST to upload a bundle to Nexus, and it's easy to
create a bundle (basically just a jar of the files to be uploaded; no need for hashes, but
sigs with a public id are needed).
+ 
+ One can either use mvn deploy -Prelease -Ptest-deploy to create all the files, sigs and
hashes under target/deploy.
+ Or "mvn verify -Prelease" will create the files and sigs (but no hashes) under target.
+ 
+ It's easy to create hashes in Ant; these are only needed for the svnpubsub/dist upload so
can be done as part of that process.
  
  == Alternative tarball process ==
  
@@ -100, +107 @@

   * if RC succeeds, tarballs still have to be moved from dist/dev to dist/release directory;
this needs a script/plugin
   * will need to update pom(s) to sign the tarballs (hopefully just once in CP)
   * update poms to create the hashes (hopefully just once in CP)
+  * deploy still adds useless .asc hashes to the staging repo.
  
  == Longshot: Update Nexus to allow it to stage tarballs as well as Maven jars ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message