I'd create a plugin that wraps your troublesome plugin with Tim Moore's awesome mojo-executor library at https://github.com/TimMoore/mojo-executor.
I just got done using it for a Real Big Client and it works great. Just have your plugin gracefully return with a warning when the environment is ripe for failure. Problem solved. Remove the plugin when MDEP-259 is fixed. HTH, Brian On Jul 10, 2011, at 9:39 AM, Brinker, Don wrote: > Hi all, > > I've got an interesting situation where I need to disable functionality for > one profile only. Well, unless of course there's a better solution to the > problem. > > In my project, we have a number of different submodules. One of these > modules (client) generates web service client JARs based on a schema file > placed in the Maven repo by a previous module (it uses dependency:copy to > pull down the schema file). Now this works all well and good unless I try to > build the site. When I do *that*, a bug in Maven (MDEP-259) makes the client > module fail outright with errors. > > My natural tendency would be just to disable the client module for the > profile used for site generation. However, we have a number of other > profiles, all of which should have this enabled. For reasons that should be > obvious, I'd really rather not define a modules block for every profile. > > Any thoughts/ideas? > > Thanks > - Don > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
