Hi Guys, Though I see this warning (while using javadoc plugin), but so far its not been a worry for me and everything is working fine. Still I had some questions for the maven experts here to get a better understanding of this...
Stephen mentioned in this thread, that it would be dangerous if the plugin:mojo is NOT removed from the forked lifecycle, since the mojo could cause yet another forked lifecycle and hence result in a recursive invocation. QUESTION 1 - Isn't the above statement only true, IF the forked-lifecyle (caused by the mojo execution) passes through (or reaches) the PARTICULARLY phase where the plugin was injected or configured to execute at the first place. For example, I know the javadoc:javadoc mojo forks a new lifecycle till the "generate-sources" phase before executing the javadoc mojo itself, now lets say If I had injected the javadoc mojo to the "install" phase, there is NO danger of recursive invocation, since the new forked-lifecyle initiated by the javadoc mojo never reaches the install phase. Yes, If instead I had hooked the javadoc:javadoc mojo to the "generate-sources" (or any of the earlier) phase , then certainly I see the execution getting stuck in a recursive loop.. Please comment... QUESTION 2 - I see the "Removing [mojo] from forked lifecycle, to prevent recursive invocation" warning only if i inject the mojo (e.g. javadoc) to the build cycle phases (be it clean, default or even site lifecyle phase) using the <build> section. If Instead I move the same definition to <reporting> section, which in other word means the plugin/mojo would only execute in the site lifecyle (if i am not wrong) then I don't see the warning at all. I wonder why is that ? Isn't the danger of recursive invocation still there (ignoring my first question) ? Thanks in advance, Farhan. Stephen Connolly-2 wrote: > > It'd be dangerous is it didn't remove the jar mojo from the forked > lifecycle, as the jar mojo is the mojo that forked the lifecycle in > the first place... and if it didn't remove the plugin from the forked > lifecycle, the forked lifecycle would fork again... and again.... and > again.... > > 2009/2/18 Romain Gilles <[email protected]>: >> Is it a dangerous for my build ? >> If yes, how can I find where the problem comes from ? >> >> Thanks, >> >> Romain. >> >> >> -----Original Message----- >> From: Brian E. Fox [mailto:[email protected]] >> Sent: 18 February 2009 01:31 >> To: Maven Users List >> Subject: RE: Removing: jar from forked lifecycle, to prevent recursive >> invocation >> >> This means the plugin that caused the fork to occur is removed from that >> forked lifecycle so it doesn't fork again. >> >> -----Original Message----- >> From: Romain Gilles [mailto:[email protected]] >> Sent: Tuesday, February 17, 2009 5:08 AM >> To: Maven Users List >> Subject: Removing: jar from forked lifecycle, to prevent recursive >> invocation >> >> >> Hi all, >> I have this message during my build process but I don't understand it: >> >> <Removing: jar from forked lifecycle, to prevent recursive invocation> >> >> It does not provide the name of the Jar, is there anybody that can help >> me, please? >> >> Romain. >> >> This email was sent to you by Thomson Reuters, the global news and >> information company. >> Any views expressed in this message are those of the individual sender, >> except where the sender specifically states them to be the views of >> Thomson Reuters. >> >> >> >> --------------------------------------------------------------------- >> 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] >> >> >> >> This email was sent to you by Thomson Reuters, the global news and >> information company. >> Any views expressed in this message are those of the individual sender, >> except where the sender specifically states them to be the views of >> Thomson Reuters. >> >> >> >> --------------------------------------------------------------------- >> 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://old.nabble.com/Removing%3A-jar-from-forked-lifecycle%2C-to-prevent-recursive-invocation-tp22054923p27264347.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]
