Hi,
> Hi,
>
> sorry for starting my newbie-career with a lot of questions...
>
> All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6
> x86.
> The layout is like this
>
> Variant A)
> testA/
> testA/pom.xml
> testMain/
> testMain/pom.xml
>
> Variant B)
> testMain/
> testMain/pom.xml
> testMain/testA/ (via svn:externals)
> testMain/testA/pom.xml
>
>
> where testMain/pom.xml hast defined testA as submodule (../testA).
>
> Now the bunch of questions/oddities:
> - On mvn release:prepare -Ddry-run=true the POMs are changed and
> testMain is checked (so no dry-run).
>   
You got the spelling wrong, it's "-DdryRun". See
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
> - How can I exclude modules from being versioned/tagged?
>   
You don't.  You need to group your projects by release cycles - only
projects that share a common release cycle should be placed under the
same parent (at least that's what I always do).
> - The scm-element is ignored in the submodule. In either variant testA
> is not tagged in subversion, in variant B) the externals point to
> trunk/testA (absolute path) or to tags/testA (relative path, not existent).
>   
Since those projects should share the same release cycle , tagging
individual sub-projects separately makes no sense (they all share the
same version number anyway).

Regards,

Tobias

> - Is there a way to call release:prepare on each (sub-)module while
> updating the changed dependencies?
>
> The reasons for using externals 1) tagging a set of modules using
> testMain's pom just for convenience and 2) refactoring takes place
> immediately on affected modules.
>
> I hope I'm not too confusing. Any help is greatly appreciated.
>
> Florian
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to