Hello, there is a phase "process-classes" in the maven build lifecycle which comes just after "compile" and is intended for post-compile work on your classes. Maybe that's what you're looking for?
Though, as Niranjan said, binding it to compile should work too (if it doesn't execute, you might need to add a <goal> definition). Yours, David Bernhard > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 09 June 2008 09:08 > To: Maven Users List > Subject: Re: Binding a plugin with a phase. > > Niranjan Deshpande schrieb: > > I want to bind the maven-antrun-plugin with maven's compile > phase. I did it > > by saying this in the plugin: > > > > <phase>compile</phase> > > > > Does this this mean that my plugin will run, after maven > has executed the > > compile phase of the life cycle? My plugin's task is > dependent on the > > compiled classes. > > > It will run *during* the compile phase, but after other plugins which > are bound to the same phase, and which were "declared earlier". The > implicit maven-compiler-plugin is "declared earlier" so your ant task > can safely assume that the code has been compiled before it runs. > > Regards, Simon > > > --------------------------------------------------------------------- > 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]
