In the interest of providing full reference in the list, I have come up with
a workaround to achieve what I want: I list the dependencies in a profile
that is active by default, then use another profile to run generate-sources
with no dependencies active, like follows:
Added in parent-prj/gen-src-
Hi Francois,
Someone on SO has explained that this is related to bug
https://issues.apache.org/jira/browse/MNG-3283
The maven-exec-plugin has "requiresDependencyResolution =
ResolutionScope.TEST"
You can see that annotation here:
https://github.com/mojohaus/exec-maven-plugin/blob/master/src/mai
Hi Alex,
maybe you could paste here the output logs of the failing execution. I'd
like them to be sure I understand the problem.
Cheers
Francois
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To unsu
Hello all,
I have a problem running exec-maven-plugin in a multi-module project
_without_ installing snapshots to my local repository. What happens is that
Maven seems to require that dependencies are "resolved" during the
"generate-sources" phase so if I run "mvn generate-sources" it complains
ab
