FYI I recall correctly... ;-)
On 21 November 2011 12:45, Stephen Connolly
wrote:
> The only way to avoid is to have the upstream modules as dependencies
> of the downstream modules... IIRC I updated dependency:copy to
> consider the reactor as a source of dependencies, in which case you
> don't h
The only way to avoid is to have the upstream modules as dependencies
of the downstream modules... IIRC I updated dependency:copy to
consider the reactor as a source of dependencies, in which case you
don't have to switch from dependency:copy to
dependency:copy-dependencies... but you will still ha
Sure, this works. But please note: we have many, many usages of this usage
style of the dependency plugin. Thus it is hard work to change each and
every location. We would like to avoid that.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-usin
the copy goal works best for dependencies outside the reactor. if your
copying dependencies from within the reactor you should use the
copy-dependencies goal instead (side effect is you will have to add the
artifacts as dependencies thus giving maven the required build ordering
info)
- Stephen
--
I'm experieting with maven-3's multi-threading feature, as it looks
promising. Unfortunately I have basic problems with the dependency-plugin
(version 2.3): We are using the copy-goal, the configuration style with
. Whenever one of these artifacts have to be built within the
same reactor, it happen
