Ahh, the "moving modules into profiles" approach is nice. Good thought.
Tim Kettler wrote:
Hi,
you have a few options to achieve what you want:
1.
I suppose you currently use the top level pom for two things:
subproject aggregation (<modules/> tag) and the definition of default
values for you subprojects (parent pom). You can just split this two
concerns in two distinct poms. For example you could create a
'myproject-parent' subproject and release just that.
2.
Maven has a command line option '--non-recursive' perhaps this does
what you want.
3.
Or you can move the <module/> definitions in a profile in the pom and
just activate it when you want to do a full release.
Hope this helps
-Tim
gc134728 schrieb:
Hey maven users,
I have a multi-module project architecture with at the top one pom.
This pom
contains several sub poms which contain sub poms ... When i perform
a release
on the top pom every project gets released with it. How can i just
perform a
release on the top pom without releasing it's subprojects with it?
One remark sometimes i do want to make a full release of top pom and all
subpoms. So what I'm looking for is a property that blocks the
transitive
release process of the maven-release-plugin.
for example : release:prepare -Dblock-reactor
Thx for any info
Yves
---
http://www.scarlet.be/
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
