Nope - expand the maven config in your project - look for the "Incremental build - only build changed modules" option.
On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: > > Scenario is this : > > Lets say one maven projects has 5 modules. > Developer changed only one module and committed it to Version control. > > Here i was looking for an option where developer and trigger build for > only this particular module. As Jenkins surely understand root pom and > modules in it and it even gives option to build individual modules but that > doesnt work for maven 3 and gives the message " Building single Maven > modules is not implemented for Maven 3, yet!" > > As per your suggestion i think you are refering to "poll scm" option in > jenkins for building only what's changed ? So lets say if i enable this > then jenkins will pull down only the files that got changed but what about > the dependencies of these files which are not changed ? Will jenkins figure > it self and bring those down too ? > > -Raj > > > On Wed, Apr 25, 2012 at 7:19 AM, M > >> What's the full use case? >> >> Also - if you're doing that - why not break them into individual >> repositories or modules and just rely on dependencies? >> >> Jenkins also has an option to "build just what's changed". Maybe that'd >> be a good compromise? >> >> >> >> >> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: >>> >>> Hi, >>> >>> Any clues when jenkins will support building individual modules for >>> maven 3 ? >>> >>> Currently it displays message " Building single Maven modules is not >>> implemented for Maven 3, yet!" >>> >>> -Raj >>> >> > On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: > > Scenario is this : > > Lets say one maven projects has 5 modules. > Developer changed only one module and committed it to Version control. > > Here i was looking for an option where developer and trigger build for > only this particular module. As Jenkins surely understand root pom and > modules in it and it even gives option to build individual modules but that > doesnt work for maven 3 and gives the message " Building single Maven > modules is not implemented for Maven 3, yet!" > > As per your suggestion i think you are refering to "poll scm" option in > jenkins for building only what's changed ? So lets say if i enable this > then jenkins will pull down only the files that got changed but what about > the dependencies of these files which are not changed ? Will jenkins figure > it self and bring those down too ? > > -Raj > > > On Wed, Apr 25, 2012 at 7:19 AM, Maven User: > >> What's the full use case? >> >> Also - if you're doing that - why not break them into individual >> repositories or modules and just rely on dependencies? >> >> Jenkins also has an option to "build just what's changed". Maybe that'd >> be a good compromise? >> >> >> >> >> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: >>> >>> Hi, >>> >>> Any clues when jenkins will support building individual modules for >>> maven 3 ? >>> >>> Currently it displays message " Building single Maven modules is not >>> implemented for Maven 3, yet!" >>> >>> -Raj >>> >> >
