-----Original Message----- >From: dan tran [mailto:[EMAIL PROTECTED] >Sent: Wednesday, April 26, 2006 5:48 PM >To: Maven Developers List >Subject: Re: Help with plugin - is this possible? > >If they are not using Continuum, ask them to use CruiseControl ;-) just kidding. Just a little humor
I hear ya. Humor appreciated. Still haven't given up - thought I might get satisfaction by adding a singleton manager created in the first phase and monitor which phases got called. But that relied on the finalize() for my manager class to be called and, of course, that doesn't happen when you need it to. :-( In reading 'Better Builds with Maven', a paragraph in section 5.2 caught my attention... "In some cases, a mojo may be designed to work outside the context of the build life cycle. Such mojos may be meant to check out a project from version control, or even create the directory structure for a new project. These mojos are meant to be used by way of direct invocation, and as such, will not have a life-cycle phase binding at all since they don't fall into any natural category within a typical build process. Think of these mojos as tangential to the the Maven build process, since they often perform tasks for the POM maintainer, or aid integration with external development tools." Can anyone explain how this is accomplished? Or am I reading more into it than is there? What I'm looking for is a way to invoke a plugin at the end of the build process, whether it was successful or not. J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
