Hi, Brett: For us a generic way to skip things could be to check if all files in the modules has been updated (through the file timestamp) and compare it to a local cache.... Some plugins already do it (xmlbeans). So why not apply this logic to the full module ? The logic could be similar to the maven option "--fail-never" except it is not an error...
Kalle: Yes, it is better to run only modules that need to, but most of the time in Eclipse we update lot of classes located in several modules. and when it is time to make a maven build we are never sure which module to run... So lot of our guys run all modules to be sure... EJ Ciramella-3: We already have our internal repository with Archiva. So we improved the artefact download phase... Thanks to all for your responses Yann. EJ Ciramella-3 wrote: > > Yeah, this is truly the solution - why not branch/aggregate the bits you > need? Set up nexus or archiva and have your own internal repository? > > -----Original Message----- > From: Kalle Korhonen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2008 5:09 PM > To: Maven Users List > Subject: Re: improve Maven performance > > Also, if only few modules see activity, wouldn't it be easy to just > release and version the stable parts separately, rather than always > building everything? > > Kalle > > > On Wed, Sep 17, 2008 at 1:59 PM, Brett Porter > <[EMAIL PROTECTED]>wrote: > >> This really needs the support of other plugins to check if they need >> to run - you can't know a generic way to skip things. For that reason >> we haven't exposed a programmatic way to do that. >> >> I would recommend focusing on what the performance bottlenecks are and > >> improving them as much as possible. >> >> - Brett >> >> 2008/9/18 Yann <[EMAIL PROTECTED]>: >> > Hi, >> > >> > In our company lot of people complains that our maven 2 builds are >> > too >> long. >> > We use multi modules and most of the time we only need to build 1 or > >> > 2 modules not all of them. >> > >> > So a solution could be to create a Maven 2 plugin that will check if > >> > a source file has changed in the module. If no file has changed then > >> > it >> will >> > skip all other phases of the module (from generate-sources to >> packaging...). >> > >> > So I know how to bind a plugin to the first maven phase (validate). >> > But how to skip all others phases without interrupted the >> > multi-module >> build >> > ? >> > >> > Thanks >> > Yann >> > >> > >> > -------------------------------------------------------------------- >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> >> -- >> Brett Porter >> Blog: http://blogs.exist.com/bporter/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/improve-Maven-performance-tp19540953p19547988.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
