After some dicotomy search on build regression it occurs that the winner is : commit 38077 (PORTAL-3273 : extends GateIn Parent)
So the use of gatein parent changed something in the build configuration.
I've attached the 2 effective-poms from each revision for the webui/eXo component (which really slows down in that case).
I still don't have a clear view of the cause for now, only a hint because install-plugin changed from 2.2 to 2.3 version.
I'm trying to see the impact of that version change.
Dimitri BAELI - eXo Platform SAS
I suppose that avoiding to build it on windows isn't a reply ??Arnaud, I made a choice, as u decsribe in up sentence. so installed
OpenSuse on my machine...hope, it will be ok with build (:
2009/10/11 Arnaud HERITIER <aheritier@gmail.com>:
--> I suppose that avoiding to build it on windows isn't a reply ??
> :-)
> Another solution can be a change in a plugin because I updated several
> things in poms.
> But the only one I'm sure I didn't change is the compiler plugin where the
> problem seems to be.
> Cheers,
>
> Arnaud
>
> # Arnaud Héritier
> # Software Factory Manager
> # eXo Platform
> # http://www.exoplatform.com
> # http://blog.aheritier.net
>
>
> On Sat, Oct 10, 2009 at 10:59 PM, Dimitri BAELI <dbaeli@gmail.com> wrote:
>>
>> Hello,
>> I already see your smile but we've got a big problem on compiling
>> GateIn on windows.
>> The issue is reported and detailled here :
>> https://jira.jboss.org/jira/browse/GTNPORTAL-27
>> The build takes 40min where it should take 5min.
>>
>> I've investigated a bit:
>> * It seems that the javac is spending all his time in scaning directories
>> in the classpath.
>> * Then I compared the dependencies of current a previous versions of
>> webui\eXo module (one of the slow modules), and it turns that nearly only
>> some versions changed in the dependencies.
>> ** There is tools.jar (12Mo !) from htmlparser from JCR (see EXOJCR-179)
>> but removing it from the compilation classpath is not sufficient.
>> ** Other dependencies changes are mainly versions changes.
>>
>> Current conclusion:
>> * It is probably a change in the classpath, but not sure yet.
>> * No clue of responsible commit for the moment.
>>
>> What's next:
>> * update the gatein source code to past revision and rebuild until the
>> commit that introduced the regression is found.
>>
>> I'm starting to study that and let you know. Unless someone has another
>> idea.
>>
>> Dimitri BAELI - eXo Platform SAS
>>
>> _______________________________________________
>> gatein-dev mailing list
>> gatein-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>>
>
>
Best regards,
Nadia
- eXo Platform SAS