I shouls read a little better before I answer questions... Forget my reply please! :-$
Roland On Thursday 08 June 2006 17:19, Roland Asmann wrote: > Hard to believe that has worked before... If the modules are BELOW the > parent (as you 'drew' it), then do NOT use '../', but just use the names. > If the modules are NEXT TO the parent, THEN you MUST use the '../'. > > Roland > > On Thursday 08 June 2006 16:48, Lee Meador wrote: > > I have my projects set up in folders all within my base folder. > > > > The parent of all the projects uses ../child1 and so forth in the > > <module> definitions. > > > > Here is the "picture" > > > > root > > + parent > > + child1 > > + child2 > > + child3 > > > > Normally, I build by going to the root and doing "mvn -f parent/pom.xml > > install". This has been working for several months. Now we have a new, > > released release plugin. > > > > When I go into the root and do 'mvn -f parent/pom.xml release:prepare" it > > given no error indications but doesn't work right. > > > > I was at 1.0-SNAPSHOT in all the projects. I was trying to release 1.0 > > and go to 2.0-SNAPSHOT. > > > > parent/pom.xmll was changed to 2.0-SNAPSHOT. all the other poms retained > > the 1.0-SNAPSHOT. Subversion got a tag (named 1.0) that contained only > > the contents of the 'parent' folder. All the other children were not > > tagged. The tag should have been one folder higher. > > > > Is there some other way to do the release that would make it work better? > > What can I check that might be causing the problems. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
