I think that this is a ClearCase specific issue. I've run into similar problems, which we solved by manually adding the label to the parent folders of 'myproject'. If you create a jira for some kind of automatic support for this, I'll vote for it. Possibly, there is one already; I haven't checked.
/Anders On Wed, Sep 2, 2009 at 09:09, <[email protected]> wrote: > Hi, > > we´re using Base ClearCase as SCM. > the scm section in the pom.xml looks like: > > ... > <scm> > <connection>scm:clearcase:load > /AAA/BBB/src/root/myproject</connection> > ... > </scm> > ... > > When releasing a project, the source is tagged, based on the > auto-generated configSpec, which looks like > > element * CHECKEDOUT > element * <tag> > element -directory * /main/LATEST > load <load_directory> > > My problem is, that the source gets only tagged beginning at 'myproject', > down the whole tree. > All elements above 'myproject' are not tagged ! > > AAA/BBB/src/root has no tags after the release. > > So when I move the project after the release to another location, I could > not properly restore the old version (for example by scm:bootstrap, using > the released pom.xml), > because the directory where the project was before does not exist anymore. > > Clearcase needs labels to the top of the loadRule, to find the version > beginning from there. > > => Any ideas ? How is that issue solved in other SCM´s, is that a > ClearCase only problem? > > Thanx all, > > torsten > > > > >
