You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by bendg <be...@gmail.com> on 2010/03/09 09:42:23 UTC
release plugin
Hi
I am running release:prepare to generate .tag and .next versions of poms.
However, some of my modules are not in the overall build.
Therefore, I need to cd into the directory to execute the release:prepare
for these modules which is not great...
Is there any way of maintaining a separate pom hierarchy for modules that I
do not want in the main build? ie. dev-build.pom.xml ?
--
View this message in context: http://old.nabble.com/release-plugin-tp27832814p27832814.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release plugin
Posted by bendg <be...@gmail.com>.
Hi Jesse,
Thanks for your reply, I have never used module tag in profiles before,
interesting idea...
Trouble is, I have a hierachy of maven modules and your suggestion would
require me to refactor my module hierarchy, which I don't want to do because
there are already in their correct areas according to their function.
Unless, there was a way, when you use <module> tag, to tell maven to execute
a different pom, ie: <module pom="dev-pom.xml"> but I don't think this is
possible.
Thanks anyway...
--
View this message in context: http://old.nabble.com/release-plugin-tp27832814p27835473.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release plugin
Posted by Jesse Farinacci <ji...@gmail.com>.
Hi Ben,
On Tue, Mar 9, 2010 at 3:42 AM, bendg <be...@gmail.com> wrote:
>
> Is there any way of maintaining a separate pom hierarchy for modules that I
> do not want in the main build? ie. dev-build.pom.xml ?
>
Even the most casual examination of the POM reference [1] would reveal:
<project>
<profiles>
<profile>
<id>dev</id>
<modules>
<module>mod1</module>
<module>mod2</module>
</modules>
</profile>
</profiles>
</project>
Where you can add additional modules via a profile. Enable the profile
with -Pdev on the command line.
[1] http://maven.apache.org/pom.html#Profiles
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release plugin
Posted by bendg <be...@gmail.com>.
Hi,
It is not my personal preference to exclude them, however, the 2 reasons
are:
1) One of the modules does not build on the build server at the moment (it
is a COTS product that we are using maven as a wrapper for). This is work
in progress for us..
2) Some of the modules are considered to be 'development time' modules that
output contents that are checked into other modules (not my choice).
but there is always a potential for a 3)
3) New module being worked on, not ready to be included in official build.
Thanks
Baptiste MATHUS-3 wrote:
>
> Jesse already answered about your solution.
> But I'm worried about what you're trying to do. Can you explain a bit why
> you don't want to include those module inside the parent one? I have some
> difficulties to understand how one could have the need to put a project
> inside a multi-module hierarchy, but without wanting to include it in this
> build hierarchy.
> Wouldn't it make more sense to extract those to-be-built-separately
> projects
> from the multi-module project?
>
> Cheers
>
> 2010/3/9 bendg <be...@gmail.com>
>
>>
>> Hi
>>
>> I am running release:prepare to generate .tag and .next versions of poms.
>>
>> However, some of my modules are not in the overall build.
>>
>> Therefore, I need to cd into the directory to execute the release:prepare
>> for these modules which is not great...
>>
>> Is there any way of maintaining a separate pom hierarchy for modules that
>> I
>> do not want in the main build? ie. dev-build.pom.xml ?
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/release-plugin-tp27832814p27832814.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
>
--
View this message in context: http://old.nabble.com/release-plugin-tp27832814p27835723.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release plugin
Posted by Baptiste MATHUS <bm...@gmail.com>.
Jesse already answered about your solution.
But I'm worried about what you're trying to do. Can you explain a bit why
you don't want to include those module inside the parent one? I have some
difficulties to understand how one could have the need to put a project
inside a multi-module hierarchy, but without wanting to include it in this
build hierarchy.
Wouldn't it make more sense to extract those to-be-built-separately projects
from the multi-module project?
Cheers
2010/3/9 bendg <be...@gmail.com>
>
> Hi
>
> I am running release:prepare to generate .tag and .next versions of poms.
>
> However, some of my modules are not in the overall build.
>
> Therefore, I need to cd into the directory to execute the release:prepare
> for these modules which is not great...
>
> Is there any way of maintaining a separate pom hierarchy for modules that I
> do not want in the main build? ie. dev-build.pom.xml ?
>
>
> --
> View this message in context:
> http://old.nabble.com/release-plugin-tp27832814p27832814.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !