I agree, just use David's release process. You can use a script or just
manually update the POM versions. It's not worth the effort to try to get the
release plugin working, since base on past experience there is a good chance you
will end up with another problem in the next release.
Jaikiran Pai wrote:
Yeah, i think David's release process is probably better. Because
with
the new release process explained in
http://community.jboss.org/wiki/MavenReleaseRepository, it looks like
the release will be directly commited to SVN repo. The earlier process
used to copy it to the local file system and then we used manually
commit it. That allowed us to decide whether or not to commit the
release, if something went wrong during the release. David's release
process provides me this flexibility.
-Jaikiran
Dimitris Andreadis wrote:
> Maybe you should consider also David's simplified release process:
>
http://community.jboss.org/wiki/DavidsMavenReleaseProcess
>
> Jaikiran Pai wrote:
>> Looks like the Maven release process for JBoss projects has now
>> changed
http://community.jboss.org/wiki/MavenReleaseRepository and
>> now use Maven Wagon SCM
>>
http://community.jboss.org/wiki/MavenReleaseRepository
>>
>> -Jaikiran
>> Jaikiran Pai wrote:
>>> 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...
>>>
>>>
>>> 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?
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development