Feature #129
Recognition of Maven Tags
| Status: | Closed | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 0.6.0 Bebhionn | |||
Description
If you use Maven to build and to create a release the tags are used a little bit different in Subversion.
The Log Message will contain:[maven-release-plugin] copy for tag XXX
/project
/tags
RELEASE-1.0
The changed files/directories etc. is a list of changed pom.xml
A /project/tags/RELEASE-1.0 /project/trunk rN R /project/tags/RELEASE-1.0/pom.xml /project/trunk/pom.xml rN+1 R /project/tags/RELEASE-1.0/x/pom.xml /project/trunk/x/pom.xml rN+1
That means that the recognition of Tag in this case is not that simple.
Related issues
| related to SupoSE - Feature #106 | Recognition of tags/branches | Closed | 10/24/2008 | ||
| related to SupoSE - Feature #190 | Recognizing Tags/Branches and index the information | Closed |
History
Updated by Karl Heinz Marbaise 1150 days ago
- Target version set to 0.5.0 Ceres
Updated by Karl Heinz Marbaise 1106 days ago
- Target version changed from 0.5.0 Ceres to 0.5.1 Europa
Updated by Karl Heinz Marbaise 1078 days ago
- Target version changed from 0.5.1 Europa to 0.5.2 Bergelmir
Updated by Karl Heinz Marbaise 1014 days ago
After checking some situations i have found out that Maven does very interesting things:
In particular in a tagged revision the following happens:Type:A /project1/tags/supose-0.0.1/pom.xml (from /project1/trunk/pom.xml revision 6) Type:A /project1/tags/supose-0.0.1/f1.txt (from /project1/trunk/f1.txt revision 2) Type:A /project1/tags/supose-0.0.1/f2.txt (from /project1/trunk/f2.txt revision 2) Type:A /project1/tags/supose-0.0.1 (from /project1/trunk revision 1)
This means that Maven uses complex tags to create the new Tag during a mvn release:prepare in the working copy from which the release:prepare has done.
Updated by Karl Heinz Marbaise 1004 days ago
- Target version changed from 0.5.2 Bergelmir to 0.6.0 Bebhionn