-
Patch
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
As far as I can see, svn-tag plugin's behaviour is strange, because if
you set the projects SCM for example to trunk and after a successful
build are going to tag it, all the modules which were checked out of the
SCM become subfolders in the tag, except for the first one.
e.g.
somerep
- trunk
- basic
- folder1
- folder2
- basic-profile
- folder3
- folder4
- basic-stuff
- ....
- tags
- tag1
- tag2
then i'm building for example the basic & basic-profile projects, the
build is successful and I'm going to tag it.
this is the result:
somerep
- trunk
- basic
- folder1
- folder2
- basic-profile
- folder3
- folder4
- basic-stuff
- ....
- tags
- tag1
- tag2
- tag3
- basic-profile
- folder3
-folder4 - folder1
- folder2
the first project to be checked out by the SCM is always deployed in the
base-directory of the tag, not in it's specific subfolders. the
following projects are then deployed in their specific subfolders. i
made a workaround, by checking out a "dummy"-project first, which is
empty, i can successfully tag the build. but if i have to check out that
build again - the "dummy" project of course is missing.
I hope you can see that this problem causes me to be not able to change
a tag or branch and build it, and if this is successful, lets me tag it
or branch it as i wish.