Re: maven-dependency-plugin fails when using maven's multi-thread feature
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 have to switch from dependency:copy to > dependency:copy-dependencies... but you will still have to add the > dependencies to your pom > > On 21 November 2011 12:19, tarand wrote: >> 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-using-maven-s-multi-thread-feature-tp5009857p5010376.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> - >> 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
Re: maven-dependency-plugin fails when using maven's multi-thread feature
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 have to add the dependencies to your pom On 21 November 2011 12:19, tarand wrote: > 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-using-maven-s-multi-thread-feature-tp5009857p5010376.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > 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
Re: maven-dependency-plugin fails when using maven's multi-thread feature
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-using-maven-s-multi-thread-feature-tp5009857p5010376.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin fails when using maven's multi-thread feature
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 --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 21 Nov 2011 08:54, "tarand" wrote: > 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 happens that the dependent artifact has not been built > before, and we encounter an "artifact-not-found" error. > > Is that a know issue with the threading feature, or do we make a mistake? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5009857.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
maven-dependency-plugin fails when using maven's multi-thread feature
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 happens that the dependent artifact has not been built before, and we encounter an "artifact-not-found" error. Is that a know issue with the threading feature, or do we make a mistake? -- View this message in context: http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5009857.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
