I'll write some docs to cover this for Apache globally, but iirc there weren't docs before for p.a.o, so the current docs have to be better than what was there previously.
Each project presumably has their own release docs similar to what we have for Maven that I've pointed projects to as they migrate. I'll make some docs but its not immediately clear where I should put them for apache wide resources. -----Original Message----- From: David Jencks [mailto:[email protected]] Sent: Wednesday, March 18, 2009 11:42 AM To: Maven Developers List Cc: Portals Discussion Subject: Re: Current status of moving apache projects to apache's nexus instance? jdcasey helped a bit on IRC, thanks. I think the documentation on this is really unsatisfactory. At least I can't find anything by googling. John pointed be to the maven release instructions http://maven.apache.org/developers/release/releasing.html which might be OK for maven components but are a bit lacking as a guide to best practices for apache projects. I've opened a jira with a few suggestions for improvements to this page http://jira.codehaus.org/browse/MNG-4095 Having the apache nexus instance there is great but I'm afraid you'll get extremely bad press if the apache 5 pom is out there and there is no trivially accessible documentation about what the consequences are of using it. For instance portals recently decided having a root pom might be a good idea and naturally chose the most recent apache pom as the parent with no awareness of the consequences about where their deployments will end up and whether or not any other steps need to be taken for other portals project release destinations. thanks david jencks On Mar 17, 2009, at 3:48 PM, David Jencks wrote: > I'm trying to help the apache portals project set up some root > poms. They are currently using the apache pom version 5 which IIUC > deploys releases and snapshots to the apache nexus instance. > > I googled but couldn't find any instructions on how to proceed with > this. I think it would be pretty handy if the maven site had a page > linked from the front page with some up to date instructions. For > instance IIUC when portals releases these poms (to nexus, right?) > all the existing portals stuff also has to be moved by hand to nexus > and all future portals releases have to go to nexus. Or did I make > this up? > > Something else I'd find pretty helpful is info on what the > recommended release profile for apache projects is and whether you > even need one or if some default is adequate. > > In case anyone wants to review the portals poms to advise on whether > they are likely to work... > > https://svn.apache.org/repos/asf/portals/portals-pom/trunk/pom.xml > https://svn.apache.org/repos/asf/portals/applications/applications-pom/t runk/pom.xml > > thanks > david jencks > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
