Hi Paul, I use the release procedure described on http://www.amdatu.org/confluence/display/Amdatu/Creating+a+release So yes, I am using the maven release plugin. Before you release RC1, I had a quick look on the code and think these minors need to be fixed;
- Add NOTICE and LICENSE files to all artifacts, as in all other Amdatu artifacts - Add copyright headers also to pom.xml files - Exported packages should have a version number Regards, Ivo From: [email protected] [mailto:[email protected]] On Behalf Of Paul Bakker Sent: dinsdag 25 oktober 2011 21:41 To: [email protected] Subject: [Amdatu-developers] maven release problem Hi all, As you might have seen from the 1001 commits I did in the past two hours, I'm trying to do a formal release of the first RC for amdatu-storage. I assume you normally use the Maven release plugin to do so. Creating a tag in subversion fails however because of insufficient permission. I believe the problem is that in the pom there is the following: <scm> <connection>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</connection> <developerConnection>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</developerConnection> <url>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</url> </scm> The developerConnection is http (not https) which can cause this problem. If I look at other POMs however, all of them just use http urls. I did try to use https, but in that case Maven gets confused because: "svn: Source and dest appear not to be in the same repository (src: 'https://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage'; dst: 'http://subversion.amdatu.org/svn/amdatu/tags/org.amdatu.storage-1.0.0-RC1')" I don't understand where the http is coming from in the destination url, it's not in the pom anymore. My question is basically, what do you use to release now? Paul
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
