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
TEST scope and since that cannot be done (I have
nothing in my local repository, nor was any output created as we were not
running the compile goal) it has no way of doing that.
Basically I think it is more a problem of exec-maven-plugin code: it clearly
asks Maven to behave like this. It should
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
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 gener
