directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot ...@marcelot.net>
Subject Re: Compiling Studio
Date Mon, 06 Sep 2010 14:40:23 GMT

On 6 sept. 2010, at 15:47, Stefan Seelmann wrote:

> Hi Pierre-Arnaud,
> 
> On Mon, Sep 6, 2010 at 2:05 PM, Pierre-Arnaud Marcelot <pa@marcelot.net> wrote:
>>> Subsequent builds don't require the activation of that profile. We
>>> changed this to speed up the subsequent builds. However this caused
>>> problems several times, maybe we should consider to revert this
>>> change.
>> 
>> Do you really think so ?
>> I think that it should be ok with an up-to-date documentation.rrrr
>> It saves a lot of time to skip the build of the 'not-code' plugins (like external
libraries, help and features plugins).
> 
> I don't think we should remove the the profile, but change the
> activation. With the following profile activtion (untested):
> 
>    ..
>    <profile>
>      <id>studio-full</id>
>      <activation>
>        <activeByDefault>true</activeByDefault>
>      </activation>
>    ...
> 
> A normal "mvn clean install" should build all modules.

You're right.

> And a "mvn clean install -P !studio-full" should deactivate the
> profile and hence skip the modules.


With the following diff, all modules are built by default and the 'not-code' plugins are excluded
when running the following command lines:
- mvn clean install -Dfastbuild
- mvn clean install -P-studio-full

> Index: pom.xml
> ===================================================================
> --- pom.xml	(revision 992968)
> +++ pom.xml	(working copy)
> @@ -133,6 +133,11 @@
>      -->
>      <profile>
>        <id>studio-full</id>
> +     <activation>
> +       <property>
> +         <name>!fastbuild</name>
> +       </property>
> +     </activation>
>        <modules>
>          <module>libraries</module>
>          <module>helps</module>


I tested this against the current trunk.

Regards,
Pierre-Arnaud


Mime
View raw message