[jboss-dev] mvn release failure

[Jaikiran Pai]

I have created a wiki which lists the issues i ran into while using the 
release plugin http://community.jboss.org/docs/DOC-14536. I had 3 
modules to release and i was finally able to release one of the modules 
using the Maven release plugin. For the remaining 2, i used David's 
release process to save time.

-Jaikiran

Jaikiran Pai wrote:
> I am now running into this same/similar issue. I am trying to release an 
> alpha of jboss-javaee-parent (and jboss-ejb-api) from here 
> http://anonsvn.jboss.org/repos/jbossas/projects/javaee/trunk/build/pom.xml 
> and Maven keeps ending up with this error:
>
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd 
> /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/javaee/trunk/build 
> && svn --non-interactive commit --file /tmp/maven-scm-1338528099.commit 
> --targets /tmp/maven-scm-4040308354544893059-targets
> [INFO] Working directory: 
> /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/javaee/trunk/build
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: Server sent unexpected return value (403 Forbidden) in response to 
> MKACTIVITY request for 
> '/repos/jbossas/!svn/act/e077bcbf-4cf0-4164-a657-db87cd13cfcd'
>
> Infact, i can't even do a "mvn clean deploy" to deploy a SNAPSHOT of 
> this project. The one common thing about all these failing projects 
> (including the one Flavia mentioned) is that they all use 5-beta-5 
> version of jboss-parent.
>
> <parent>
> <groupId>org.jboss</groupId>
> <artifactId>jboss-parent</artifactId>
> <version>5-beta-5</version>
> </parent>
>
> And looking at that pom 
> http://repository.jboss.org/maven2/org/jboss/jboss-parent/5-beta-5/jboss-parent-5-beta-5.pom 
> i see that there have been major changes to the distributionManagement 
> section since jboss-parent-4/jboss-parent-5-beta-1:
>
> <distributionManagement>
> <repository>
> <id>jboss-releases</id>
> <name>JBoss Release Repository</name>
> <url>${jboss.releases.repo.url}</url>
> </repository>
> <snapshotRepository>
> <id>jboss-snapshots</id>
> <name>JBoss Snapshot Repository</name>
> <url>${jboss.snapshots.repo.url}</url>
> </snapshotRepository>
> </distributionManagement>
>
>
> It now uses 2 different ids "jboss-releases" and "jboss-snapshots" for 
> the distribution management repositories. Earlier, it was 
> "repository.jboss.org" and "snapshots.jboss.org". That explains why my 
> snapshot deploy failed - it couldn't find a corresponding server for 
> username/password in settings.xml. I had to add this in settings.xml to 
> get the SNAPSHOT deploy working.
> <server>
> <!-- Configuration of the webdav access to the snapshots repository -->
> <id>jboss-snapshots</id>
> <username>myusername</username>
> <password>mypass</password>
> </server>
>
> Looks like Paul has updated the MavenSettingsExample[1] wiki to reflect 
> this change.
>
> However, this doesn't explain why the tagging during release is failing. 
> I do see another change in the "jboss-releases" distribution management 
> repository config for jboss-parent-5-beta-5:
>
> <distributionManagement>
> <repository>
> <id>jboss-releases</id>
> <name>JBoss Release Repository</name>
> <url>${jboss.releases.repo.url}</url>
> </repository>
>
> and the ${jboss.releases.repo.url} points to:
>
> <jboss.releases.repo.url>scm:svn:https://svn.jboss.org/repos/repository.jboss.org/maven2</jboss.releases.repo.url>
>
> In the earlier versions, this used to point to the local checkout of the 
> maven repo:
>
> <distributionManagement>
> <repository>
> <!-- Copy the distribution jar file to a local checkout of the maven 
> repository
> - This variable can be set in $MAVEN_HOME/conf/settings.xml -->
> <id>repository.jboss.org</id>
> <url>file://${maven.repository.root}</url>
> </repository>
>
> Not sure if this is causing the release issues. Maybe Paul knows?
>
> [1] http://community.jboss.org/wiki/MavenSettingsExample
>
>
> Flavia Rainone wrote:
>> I had a similar failure when doing the classpool release, but it was not 
>> same error as you (can't tag it cause the message was repository does 
>> not exist).
>> This is what I've done:
>> - I checked that I forgot to define my username and password
>> - During the first release try, the pom was updated and for some strange 
>> reason, I got an error and the scm address moved from trunk to tag 
>> (don't ask me why). I had to fix my pom then.
>> - downgraded the version of release plugin to 2.0-beta-8
>>
>> Downgrading didn't work for me as the other two points were the cause of 
>> the problem. But I found an e-mail thread on the web that mentioned that 
>> 2.0-beta-9 has a bug and that causes maven to not be able to tag it. 
>> That's why I gave it a try. Maybe this will solve your problem?
>>
>> On 12/19/2009 04:54 PM, Ales Justin wrote:
>>> Any idea what might be wrong?
>>> Or is this just one of those "mvn release:x" random failures?
>>>
>>> ---------------------------------------------------------------------
>>>
>>> [INFO] Tagging release with the label 1.0.0.Alpha1...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>> C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision
>>> 98027
>>> https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-parent-4/mcann-build
>>> https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1"
>>> [INFO] Working directory: C:\projects\microcontainer\mc-ann
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Unable to tag SCM
>>> Provider message:
>>> The svn tag command failed.
>>> Command output:
>>> svn: Repository moved permanently to 'https://svn.jboss.org/repos/';
>>> please relocate
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>    
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development