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: [email protected] For additional commands, e-mail: [email protected]
