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 "UsingNexus" by sebbapache
Date Thu, 19 Aug 2010 11:01:08 GMT
Dear Wiki user,

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

The "UsingNexus" page has been changed by sebbapache.
http://wiki.apache.org/commons/UsingNexus?action=diff&rev1=15&rev2=16

--------------------------------------------------

  
  ==== Releasing ====
  
+ '''NOTE''' The Commons Parent pom currently attaches the assembly archives (the -bin* and
-src* files) to the deploy phase, so they end up being copied to the Nexus staging repository.
This is convenient for voting, as all the files are in the same place, but means that additional
action needs to be taken to move the non-Maven files to the correct place.
+ 
- ===== wget the artifcats from nexus to people server =====
+ ===== wget the non-Maven artifacts from Nexus to people server =====
  
  In your home directory, perform: 
  {{{
@@ -339, +341 @@

  symlinks.sh 1.2
  }}}
  
- were the argument is the number of your version.
+ where the argument is the number of your version.
  
- ===== Nexus relase =====
+ ===== Nexus release =====
  
   1. remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus staging
area
   1. [[http://www.apache.org/dev/publishing-maven-artifacts.html#promote|Promote]]
+ 
+ Note that Nexus release is asynchronous - it may take a short while for the files to be
copied to the release area of Nexus and for the status to be updated.
+ 
+ It may take a while for the Maven repo to be synchronised from Nexus. Sometimes the files
don't all appear at once.
  
  ===== Test =====
  
@@ -365, +371 @@

  mvn site:deploy
  }}} 
  
+ On people.apache.org, verify that the directory has been updated, and that the file and
directory permissions are correct (readable by all, not writeable by world, but group writeable).
Also, ensure that the group is set to 'commons'. For example:
+ 
+ {{{
+ pwd commons.apache.org : ls -l compress
+ total 1366
+ drwxrwsr-x  5 niallp     commons      20 Aug 19 07:22 apidocs
+ -rw-rw-r--  1 grobmeier  commons   21050 Aug 19 09:19 changes-report.html
+ drwxrwsr-x  5 niallp     commons      98 Aug 19 07:22 cobertura
+ -rw-rw-r--  1 grobmeier  commons    7555 Aug 19 09:19 conventions.html
+ }}}
+ 
- On people.apache.org, verify that the directory has been updated, and that the file and
directory permissions are correct (readable by all, not writeable by world, but group writeable).
Note that the files are transferred to the real web site only every few hours, so it may be
a while before you see your changes appear. However if you set your webbrowser's HTTP proxy
to 140.211.11.10 port 80 and access http://commons.apache.org/ you should be able to see the
changes immediately.
+ Note that the files are transferred to the real web site only every few hours, so it may
be a while before you see your changes appear. However if you set your webbrowser's HTTP proxy
to 140.211.11.10 port 80 and access http://commons.apache.org/ you should be able to see the
changes immediately.
  
  ===== Send announcement =====
  
  Announce the availability of the new release.
+ Please check that the mirrors have been updated with the new release before sending the
announce.
+ There is no need to check all mirrors, but it's worthwhile checking a few of them.
  
  Please remember to give a brief description of your component. Please also remember to remind
people about verifying the signatures. The subject should be something like [ANNOUNCEMENT]
Foo 1.2 Released. Send this mail from your Apache account. Please spell check the document!
  

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


Mime
View raw message