Hello Martin, Yes, that's it: when m-site-p launches reporting plugins that require lifecycles, it seems that lifecycles can be relaunched multiple times. I still don't know where is the bug, or where to fix things: Maven Core, m-site-p or reporting plugins
So please remove site building in your Jenkins jobs Regards, Hervé Le dimanche 13 avril 2014 17:44:45 Martin Desruisseaux a écrit : > Hello Hervé > > Le 13/04/14 17:35, Hervé BOUTEMY a écrit : > > there are problems when building site, with reports forking lifecycles > > multiple times > > can you try without building site? > > A "mvn install" or a "mvn deploy" works well. The multiplication appears > when the "site" phase is included. So this issue is worrying "only" for > Jenkins. Of course we could remove the site phase in our Jenkins job if > that could help: this reduce the build time a lot. > > Martin > > > Le dimanche 13 avril 2014 16:07:20 Martin Desruisseaux a écrit : > >> Hello all > >> > >> An other aspect which may be worth to explore for reducing resource > >> consumption is the way we use or configure Maven. A few weeks ago, > >> executing "mvn clean install deploy site" on Apache SIS with Maven 3.1 > >> apparently trigged compilation of all source code 18 times. It may not > >> be Maven fault - I suspect some interactions between plugins, not all of > >> them developed at Apache. The situation seems to improve with Maven 3.2 > >> (still need to confirm). > >> > >> Martin
