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 artifactItems. Whenever one of these artifacts have to be built within the same

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

Migrating plugin to maven 3

Hi, I am using today maven 2, and would like to migrate to maven 3. I am having few plugins that I compile for my usage, in maven 2. My question is- what is the migration procedure to use them in Maven 3 as well? Thanks -- View this message in context:

Re: Migrating plugin to maven 3

They should just work. M3 is supposed to be 99.999% compat with m2 Note the 0.001 is to cover the hacks people have used that they shouldn't On 21 November 2011 09:42, Eyal Goren eyalg1...@gmail.com wrote: Hi, I am using today maven 2, and would like to migrate to maven 3. I am having few

Migration plugin from maven 2 to maven 3

Hi, I would like to start migrating our maven projects to maven 3, the issue is the plugins we are creating. What is the procedure to migrate plugins to maven 3? or we should just build them with Maven 3? Thanks -- View this message in context:

Re: Migrating plugin to maven 3

Hi, So- we don't need to re-compile them again using maven 3? just try and run? -- View this message in context: http://maven.40175.n5.nabble.com/Migrating-plugin-to-maven-3-tp501p5010205.html Sent from the Maven - Users mailing list archive at Nabble.com.

Re: Migrating plugin to maven 3

no need to recompile... there is a need to re-test but not a major one! On 21 November 2011 11:05, Eyal Goren eyalg1...@gmail.com wrote: Hi, So- we don't need to re-compile them again using maven 3? just try and run? -- View this message in context:

Re: Workaround for manifestEntry bug

Hi Jan, honyk wrote: Hello Everyone, I've refactored my ant-based library into maven based one, but I've encounter the same issue reported as the blocker here: http://jira.codehaus.org/browse/MSHARED-182 Seeing the date of creation of this ticket I suppose there is no prospect of quick

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:

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

Re: maven-dependency-plugin fails when using maven's multi-thread feature

FYI I recall correctly... ;-) On 21 November 2011 12:45, Stephen Connolly stephen.alan.conno...@gmail.com 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

versions plugin does not show the maven-jar-plugin 2.3.2 as a new version

Hi! I'm using maven 3.0.3, which uses the maven-jar-plugin 2.3.1 as default (predefined in the super pom I think). If I run a mvn versions:display-plugin-updates then the maven-jar-plugin 2.3.2 does not shows in the list. Is it because I'm not explicitly declaring the use of the jar plugin in

maven-war-plugin Dojo Build file being overwritten by the war plugin

The situation is that our web app has a /js directory containing our custom JavaScript application files. In our release profile we are running a dojo build that copies the src/js files into target/dojo-build and using maven exec plugin to run the build. The built files are then copied into

plugin goal wont execute during process-test-resources phase

Hi I am fairly new to configuring maven and i need to execute a goal of a plugin but it wont execute when i do mvn process-test-resources. It seems that the plugin goal is somehow unbound from the plugin phase. I am attaching pom.xml here. thanks for the help. project

How to include the *-sources.jar in a binary distribution?

Hi, I'd like to include the *-sources.jar in a lib-src/ directory in my binary distribution (done via assembly) [1]. The reason why I'd like to include the *-sources.jar in the binary distribution is because people using IDEs (and not Maven) can point at them and browse the sources of our

Maven surefire 2.11 release date

I noticed that Maven Surefire 2.10 was released this past september. In jira there are 8 issues associated with 2.11, all of which are closed. Is there any sense on when 2.11 will be sent for a vote on release? I'm particularly interested in the Junit Category support in the

Re: Maven surefire 2.11 release date

i cannot recall if kristian is aiming fir an 8 or 12 week average cycle... but it is likely to be close to one of those... we are volunteers you know ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using

Maven Surefire 2.11 release date

I noticed that Maven Surefire 2.10 was released this past september. In jira there are 8 issues associated with 2.11, all of which are closed. Is there any sense on when 2.11 will be sent for a vote on release? I'm particularly interested in the Junit Category support in the

Re: How to include the *-sources.jar in a binary distribution?

Paolo, Are the -sources an artifact of the same project that is running the assembly plugin? Off hand I'd suggest making a separate module to build the combined sources jar, and then you should be able to pull that into the assembly. Or, just use a file pointing at the right file in target/

Re: How to include the *-sources.jar in a binary distribution?

On Tue, Nov 22, 2011 at 6:35 AM, Paolo Castagna castagna.li...@googlemail.com wrote: Hi, I'd like to include  the *-sources.jar in a lib-src/ directory in my binary distribution (done via assembly) [1]. The reason why I'd like to include the *-sources.jar in the binary distribution is because

Re: How to include the *-sources.jar in a binary distribution?

Hi Benson, the lib/ directory includes: - jena-arq-2.8.9-incubating-SNAPSHOT.jar - jena-core-2.6.5-incubating-SNAPSHOT.jar - jena-iri-0.9.0-incubating-SNAPSHOT.jar - jena-larq-1.0.0-incubating-SNAPSHOT.jar - jena-tdb-0.9.0-incubading-SNAPSHOT.jar Each of the modules (i.e. jena-arq,

Re: How to include the *-sources.jar in a binary distribution?

Then I think the other hint about classifier syntax is more to the point. Could I reproduce your problems by co'ing the jena trunk tree and fooling around? On Mon, Nov 21, 2011 at 7:03 PM, Paolo Castagna castagna.li...@googlemail.com wrote: Hi Benson, the lib/ directory includes:  -

How to list only Reactor build order

Hi, I want to list only reactor build order. Is there ant mvn reactor option or anyother way to list only reactor build order? Thanks, Babji