With version 2.3 of the m-dependency-p the copy and unpack goals will now resolve from the reactor.
you seem to be using dependency:copy-dependencies and not dependency:copy if you are referring to MDPE-259 If you replace dependency:copy-dependencies with dependency:copy you can use the artifactItem to refer exactly to the schema file that you are attaching to the reactor rather than having to pull in the jar file... Another solution would be to bind jar:jar to the pre-site phase in the module in question (so that the packaged jar is available in a multi-module site generation. On 10 July 2011 17:39, Brinker, Don <dbrin...@collegeboard.org> 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
