2:26 a.m.
For me we are many to have this issue : Ukraine team, me. That's why I
spent some time on that.
Here is my build sumary for gatein "mvn clean install" on windows
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] eXo Portal Config ..................................... SUCCESS
[2.141s]
[INFO] eXo Portal Common ..................................... SUCCESS
[4.344s]
[INFO] Portal Resource ....................................... SUCCESS
[7.500s]
[INFO] GateIn PC integration ................................. SUCCESS
[10.281s]
[INFO] XML Parser ............................................ SUCCESS
[5.031s]
[INFO] GateIn WSRP integration ............................... SUCCESS
[16.203s]
[INFO] exo.portal.component.scripting ........................ SUCCESS
[5.406s]
[INFO] eXo portal component web .............................. SUCCESS
[23.782s]
[INFO] JBoss Identity IDM integration ........................ SUCCESS
[3.875s]
[INFO] eXo Portal Data ....................................... SUCCESS
[2:39.547s]
[INFO] eXo Application Registery Service ..................... SUCCESS
[1:46.906s]
[INFO] eXo portal webui core ................................. SUCCESS
[35.141s]
[INFO] eXo portal webui eXo .................................. SUCCESS
[1:40.469s]
[INFO] eXo Gadgets Config .................................... SUCCESS
[0.015s]
[INFO] eXo Gadgets Core ...................................... SUCCESS
[23.157s]
[INFO] eXo portal webui core ................................. SUCCESS
[5:02.578s]
[INFO] exo-portal.component.dashboard Portlet ................ SUCCESS
[2:29.203s]
[INFO] eXo Gadgets Web App ................................... SUCCESS
[0.687s]
[INFO] eXo Gadgets Application ............................... SUCCESS
[0.891s]
[INFO] exo-portal.portlets.exoadmin Portlet .................. SUCCESS
[4:13.047s]
[INFO] exo-portal.portlets.web Portlet ....................... SUCCESS
[1:42.609s]
[INFO] exo-portal.portlets.dashboard Portlet ................. SUCCESS
[2:19.063s]
[INFO] eXo Portal Resources .................................. SUCCESS
[25.312s]
[INFO] eXo REST web application .............................. SUCCESS
[0.235s]
[INFO] eXo Portal web module ................................. SUCCESS
[31.687s]
[INFO] eXo Tomcat Server ..................................... SUCCESS
[0.391s]
[INFO] eXo Tomcat Server ..................................... SUCCESS
[0.234s]
[INFO] eXo JBoss Server ...................................... SUCCESS
[0.437s]
[INFO] eXo JBoss Server ...................................... SUCCESS
[0.516s]
[INFO] eXo Tomcat Server ..................................... SUCCESS
[0.172s]
[INFO] eXo Portal Packaging .................................. SUCCESS
[13.609s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 25 minutes 25 seconds
[INFO] Finished at: Sun Oct 11 18:02:33 CEST 2009
[INFO] Final Memory: 65M/258M
[INFO]
------------------------------------------------------------------------
Dimitri BAELI - eXo Platform SAS
On Sun, Oct 11, 2009 at 10:34 PM, Arnaud HERITIER <aheritier(a)gmail.com>wrote:
I don't know who committed this one :-)
Is there someone on windows who have the same issue in another gatein
component ?
I studied your 2 poms and effectively I don't see something which could be
related to our issue.
If need we can try to debug Maven itself to see what it does.
Arnaud
On Sun, Oct 11, 2009 at 5:43 PM, Dimitri BAELI <dbaeli(a)gmail.com> wrote:
> 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
>
>
> On Sun, Oct 11, 2009 at 1:19 PM, Nadia Zavalko <
> nadejda.zavalko(a)exoplatform.com> wrote:
>
>> 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(a)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(a)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(a)lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/gatein-dev
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Best regards,
>> Nadia
>> - eXo Platform SAS
>>
>
>