[
http://jira.amdatu.org/jira/browse/AMDATU-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff resolved AMDATU-138.
------------------------------------
Resolution: Fixed
Done in scope of mvn221 (not fully tested mvn302). Assuming you have dav access
to scm and the amdatu repository you can now:
1) Create an arbitrary branch with custom version (interactive)
> mvn branch -DbranchName=helloworld
2) Release and tag a new version (interactive)
mvn release:prepare
3) Deploy a released version (from a project where you just ran prepare)
> mvn release:perform
4) Deploy a released version (from any scm tag)
> mvn release:perform -DconnectionUrl=<scmUrl>
5) Deploy a snapshot release from any branch
> mvn deploy
For now the site is deployed from the trunk, not from the release cycle. I'll
update th wiki a little later.
> Configure and use release plugin for releasing
> ----------------------------------------------
>
> Key: AMDATU-138
> URL: http://jira.amdatu.org/jira/browse/AMDATU-138
> Project: Amdatu
> Issue Type: Improvement
> Components: Build & Release management
> Affects Versions: 0.0.5
> Reporter: Bram de Kruijff
> Assignee: Bram de Kruijff
> Fix For: 0.2.0
>
>
> The maven release plugin automates updating pom versions, branching and
> tagging and running (integration) tests in reactor while your at it. Makes
> life easier and reduces chances of human error like this one
> http://subversion.amdatu.org/viewvc/tags/0.0.5-RC1/?root=amdatu ;)
> http://maven.apache.org/plugins/maven-release-plugin/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
