Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.18
-
Fix Version/s: 1.19
-
Component/s: None
-
Labels:None
Description
Enunciate Maven Plugin neglects "provided" scoped artifacts.
The way how ConfigMojo gathers runtimeClasspath means, that dependencies with scope "provided" are simply left out.
1) If Maven3 only is to be supported, the fix is to change @requiresDependencyResolution compile+runtime on ConfigMojo.
2) If Maven2 and Maven3 is targeted, then @requiresDependencyResolution test helps only, but it requires manual removal of "test" scoped artifacts.
Since the manual removal is already implemented, I am going for solution 2).
Patch fixing multiple issues:
The patch is made against rev888 of trunk, base of patch is https://svn.codehaus.org/enunciate/trunk/enunciate
- forking Mojo, hence doubling lifecycle execution
- getting "provided" scoped artifacts onto Enunciate classpath
The patch is made against rev888 of trunk, base of patch is https://svn.codehaus.org/enunciate/trunk/enunciate