Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency resolution should be optional #106

Open
karypid opened this issue May 20, 2018 · 0 comments
Open

Dependency resolution should be optional #106

karypid opened this issue May 20, 2018 · 0 comments

Comments

@karypid
Copy link

karypid commented May 20, 2018

Hello,

I am writing to raise awareness to an issue in exec-maven-plugin that prevents it from being used in the generate-sources phase. The problem is that it uses "requiresDependencyResolution = ResolutionScope.TEST" (see: https://github.com/mojohaus/exec-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/exec/ExecJavaMojo.java) which means that it cannot be invoked before the compile phase (even though a typical use of this plugin is in generate-sources to invoke code generators).

Basically, I think that the annotation should be removed and replaced with programmatically checking whether dependencies are available when "includeProjectDependencies" in the configuration is true.

Resources:

[1] Issue raised in Maven side: https://issues.apache.org/jira/browse/MNG-3283

[2] My SO question: https://stackoverflow.com/questions/50288587/how-does-maven-decide-when-to-use-the-target-folder-for-classpath

[3] Discussion in Maven user list: http://maven.40175.n5.nabble.com/Problem-with-exec-maven-plugin-td5934208.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant