| 32 |
|
MRELEASE-271
|
perform goal sometimes fails with multi-module projects
|
|
|
|
| 27 |
|
MRELEASE-516
|
release:prepare should support a nested/flat hybrid SCM structure
|
|
|
|
| 18 |
|
MRELEASE-100
|
implement release:release goal
|
|
|
|
| 17 |
|
MRELEASE-252
|
Support for multi modules project
|
|
|
|
| 15 |
|
MRELEASE-123
|
release plugin does not take commandline parameters into account
|
|
|
|
| 15 |
|
MRELEASE-285
|
Unresolved test-jar dependency during release
|
|
|
|
| 14 |
|
MRELEASE-263
|
Interactive plugins cannot work in forked executions
|
2.5 |
|
|
| 11 |
|
MRELEASE-161
|
If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated
|
|
|
|
| 11 |
|
MRELEASE-581
|
Git relative pathing broken with release plugin
|
|
|
|
| 9 |
|
MRELEASE-220
|
Add property to keep released versions for dependencies
|
|
|
|
| 9 |
|
MRELEASE-241
|
Need a tagByProject that works like commitByProject
|
Backlog |
|
|
| 8 |
|
MRELEASE-595
|
release:prepare using old SVN structure when creating tag
|
|
|
|
| 7 |
|
MRELEASE-679
|
CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
|
|
|
|
| 7 |
|
MRELEASE-181
|
During the release:prepare goal this plugin should check if released versions of SNAPSHOT dependencies exist before failing.
|
|
|
|
| 7 |
|
MRELEASE-444
|
Prepare in multi-module project update the snaphsot version to release version only in one of the submodule
|
|
|
|
| 7 |
|
MRELEASE-548
|
release:prepare can't resolve snapshot dependencies in batch mode
|
|
|
|
| 7 |
|
MRELEASE-649
|
release:prepare - ignores SNAPSHOT version in pluginManagement section
|
|
|
|
| 7 |
|
MRELEASE-707
|
release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
|
|
|
|
| 6 |
|
MRELEASE-512
|
SCM information should be validated
|
|
|
|
| 6 |
|
MRELEASE-695
|
tagNameFormat with @{project.version} tags the SNAPSHOT version
|
|
|
|
| 5 |
|
MRELEASE-129
|
Release fails on EAR project with EJB module reference
|
|
|
|
| 5 |
|
MRELEASE-216
|
Release plugin should ignore SNAPSHOTS that are not specified in the POM
|
|
|
|
| 5 |
|
MRELEASE-378
|
Check snapshots phase ignores plugin dependencies
|
|
|
|
| 5 |
|
MRELEASE-399
|
Replace dependency version for <version>RELEASE</version> dependency.
|
|
|
|
| 5 |
|
MRELEASE-401
|
release:prepare should create the SVN tags parent dir if it doesn't already exist, rather than failing
|
|
|
|
| 5 |
|
MRELEASE-620
|
NPE on a range dependency
|
|
|
|
| 4 |
|
MRELEASE-715
|
Impossible to release projects which have compiler args such as Xlint:all
|
|
|
|
| 4 |
|
MRELEASE-218
|
Check if properties contains SNAPSHOT
|
Backlog |
|
|
| 4 |
|
MRELEASE-494
|
Should fail during release:prepare if scm:url doesn't match working copy
|
|
|
|
| 4 |
|
MRELEASE-549
|
Pin svn:externals when tagging
|
|
|
|
| 4 |
|
MRELEASE-562
|
release:prepare uses incorrect tag source on multi-module projects
|
|
|
|
| 4 |
|
MRELEASE-719
|
No error when release:prepare with an already existing scm tag
|
2.5 |
|
|
| 4 |
|
MRELEASE-174
|
mvn release:prepare will not tag in subversion repository
|
|
|
|
| 4 |
|
MRELEASE-576
|
Subversion Tag is incorrect when releasing from a Branch
|
|
|
|
| 3 |
|
MRELEASE-717
|
Releases from HG fail if project is not in root of repository
|
|
|
|
| 3 |
|
MRELEASE-230
|
release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies
|
|
|
|
| 3 |
|
MRELEASE-391
|
Improve staging support
|
|
|
|
| 3 |
|
MRELEASE-410
|
Allow specifying specific profiles to execute in the prepare mojo
|
|
|
|
| 3 |
|
MRELEASE-594
|
release:prepare should stop when there is snapshots in dependencies management
|
Backlog |
|
|
| 3 |
|
MRELEASE-106
|
Remember the Dry Run Status
|
Backlog |
|
|
| 3 |
|
MRELEASE-148
|
Add prompts to input parent POM release version and next development version
|
|
|
|
| 3 |
|
MRELEASE-283
|
Plugin configuration is not rewritten to release-pom.xml if <inherited>false</..>
|
|
|
|
| 2 |
|
MRELEASE-126
|
Break during release if any dependency does not have pom
|
|
|
|
| 2 |
|
MRELEASE-206
|
its not possible to pass MAVEN_OPTS to the forked release build
|
Backlog |
|
|
| 2 |
|
MRELEASE-282
|
Replace the current 'arguments' parameter with specialized version for each mojo (eg. 'argumentsRelease')
|
|
|
|
| 2 |
|
MRELEASE-284
|
prepare step should check if local sources are complete
|
|
|
|
| 2 |
|
MRELEASE-353
|
release:prepare failed after a refactoring
|
|
|
|
| 2 |
|
MRELEASE-431
|
Configuration of policy for calculating next (release) version
|
|
|
|
| 2 |
|
MRELEASE-567
|
mvn release:prepare fails with missing artifacts when running assembly
|
|
|
|
| 2 |
|
MRELEASE-668
|
Properties are not inherited
|
|
|
|