You could try to use an include and exclude policy for both plugins based on some pattern. You could also try a lifecycle approach and sort the lifecycle steps properly. Also we are adding that capability to the Weblogic plugin at codehaus but just trying to get it checked in and into the next release.
Scott Ryan [EMAIL PROTECTED] (303) 263-3044 On Tue, Mar 11, 2008 at 1:37 PM, SingleShot <[EMAIL PROTECTED]> wrote: > > I am writing a custom Maven plugin that wraps a code generation tool > (BEA's > Java Web Service Compiler for Weblogic Server). The tool takes in java > source files and generates java class files (i.e. it is a compiler). The > class files are different from what the "normal" Java compiler generates. > I > have attached it to the compile phase of the normal build lifecycle. One > issue I have is that the java class files get generated twice: once by the > maven-compiler-plugin, and once by my custom plugin. I end up with two > sets > of class files that are different (they are generated to different > locations > by default). There are a couple of hacks I can do to solve this, but what > I > really want is for my plugin to be used in place of the > maven-compiler-plugin, and only for a particular module within my > hierarchy > of modules. Is there a way to configure a project and/or its plugins to > say > "normally you should use the maven-compiler-plugin to compile, but in this > one particular case, use my custom plugin instead"? > > Any suggestions would be appreciated. Thanks, > > Mike > -- > View this message in context: > http://www.nabble.com/Substitute-One-Plugin-for-Another--tp15988286s177p15988286.html > Sent from the Maven - Users mailing list archive at > Nabble.com<http://nabble.com/> > . > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
