Hi Matt, Thanks for offering to help with Airavata release. I think I figured out the mistake. I am trying to release from a branch but forgot to update the SCM tag to point to branch. And probably the maven was picking the trunk pom and adding the snapshot prefix in nexus. I now updated the scm to right branch and the release seems to be going well.
Thanks, Suresh On May 29, 2012, at 10:19 AM, Franklin, Matthew B. wrote: > I will take a look later today. > > From: Suresh Marru [mailto:[email protected]] > Sent: Monday, May 28, 2012 11:35 PM > To: Franklin, Matthew B. > Subject: help with airavata release pom > > Hi Matt, > > Will you be able to help with airavata release verification? > > I released Airavata 0.2 release just fine but maven release pom has been > irritating me for 0.3 release. The dry run steps show all files correctly. > When I do a release prepare, the attached release properties is created which > has all versions listed correctly. But when maven created the tag pom, it for > some reason updates it to development version (0.4). > > I will greatly appreciate if you can let me know whats going wrong. The > created tag is - > https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.3-incubating/ > > The branch I am trying to do the release from - > https://svn.apache.org/repos/asf/incubator/airavata/branches/0.3-incubating-snapshot/ > > Thanks, > Suresh >
signature.asc
Description: Message signed with OpenPGP using GPGMail
