Hi, I discovered some problems especially with tagging with this structure.
The best way I came to till now is to make a further multi-module-pom above all the modules, which only - specify scm settings - include one multi-module pom which includes all the others (myapp-parent in your case if it includes the other ones) The way to the further pom mainly resolves from the disability to edit the pom with eclipse without checking out the whole tree. So the structure I use is pom.xml (multi-module, include only the app-modules) -- app-modules -- -- pom.xml (include module1, module2) -- module1 -- -- pom.xml -- module2 -- -- pom.xml I tried to start the release-plugin from the folder above the modules and specify the pom as app-modules/pom.xml but it seems that the release-plugin is not able to work with it - so I added the top-level-pom. Regards Michael Am Samstag, den 24.10.2009, 10:41 -0500 schrieb Neil Chaudhuri: > I have a flat multi-module project as follows: > > myapp-parent > --pom.xml > myapp-persistence > --pom.xml > myapp-services > --pom.xml > > The parent module is simply inherited by the others, and services aggregates > persistence. > > I am using SVN SCM and Maven Release Plugin 2.0-beta-9. My goal with each > release is simply to create a folder in the tags directory that looks as > follows: > > <SVN ROOT>/myapp/tags/ > --myapp-0.8.0 > ----myapp-parent-0.8.0 > ------<All parent files> > ----myapp-persistence-0.8.0 > ------<All persistence files> > ----myapp-services-0.8.0 > ------<All services files> > > When I run the Maven Release Plugin at the parent pom level, all I get is > this: > > <SVN ROOT>/myapp/tags > --myapp-parent-0.8.0 > ----<All parent files> > > Even though it may not be obvious from the high art of dash indentation, I > have two problems: > 1) The parent module is not contained in some "larger" folder beneath > myapp-0.8.0/tags. > 2) It is only the parent module being tagged. > > Here is my configuration of the plugin in the parent pom: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.0-beta-9</version> > <configuration> > > <updateWorkingCopyVersions>false</updateWorkingCopyVersions> > <goals>clean install</goals> > <arguments>-Dmaven.test.skip</arguments> > <tagBase>svn://<svn root>/<myapp>/tags</tagBase> > </configuration> > </plugin> > > After doing some research, I discovered the following: > http://jira.codehaus.org/browse/MRELEASE-261. Here it says that Maven Release > Plugin 2.0-beta-10 should support multi-module projects and that in fact the > issue I an seeing is closed. > > At long last, here are my questions: > > 1) Is my desired tag structure (myapp-0.8.0 folder beneath tags and > containing all the flat modules) possible with the currently released plugin? > How would I do it? > 2) Is the fact I am not tagging the other modules a result of the same issue > addressed by that JIRA page, or am I mixing things up and just doing > something wrong with my current configuration? > 3) Will what I want be possible with the next version? When is the next > version due? > > Please let me know if I need to clarify anything. I appreciate your insight. > > Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
