I am not sure what can be done here, to be honest. The javadoc jar is on
build classpath, so m2e correctly puts it on compile classpath. Problem
is, Maven does not have proper model for attached artifacts, so m2e has
no way to determine the contents of javadoc jar and just adds entire
project.
--
Regards,
Igor
On 12-10-12 1:08 PM, Chris Conroy wrote:
On Fri, Oct 12, 2012 at 12:37 PM, Igor Fedorenko <[email protected]
<mailto:[email protected]>> wrote:
Can you check build classpath for myproject-subproject either with
dependency:build-classpath or by running the build with -X parameter? I
want to know if the javadoc jar is on classpath or not.
mvn depdency:build-classpath shows the javadoc jar is on the build
classpath.
--
Chris Conroy
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
