[jira] (MJAVADOC-424) Compile errors and warning when generating the test-javadoc
[ https://jira.codehaus.org/browse/MJAVADOC-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365079#comment-365079 ] Michal Srb commented on MJAVADOC-424: - I believe that this is a same issue as in MJAVADOC-414. > Compile errors and warning when generating the test-javadoc > --- > > Key: MJAVADOC-424 > URL: https://jira.codehaus.org/browse/MJAVADOC-424 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10.1 >Reporter: Jim Sellers > > With the changes to the classpath done in MJAVADOC-398 and MJAVADOC-406, this > means now I get javadoc warnings and errors when creating a site. The errors > fail the build. > This showed up because code in src/test/java used constants defined in > src/main/java. > Work around was to revert to 2.9.1 > {code:XML|title=Sample pom snipit} > > > > > org.apache.maven.plugins > maven-javadoc-plugin > > 2.10.1 > > false > true > > > > > > > > > org.apache.maven.plugins > maven-javadoc-plugin > > false > true > > > > default > > javadoc > test-javadoc > > > > > > > {code} -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-414) Artifacts missing from test classpath.
[ https://jira.codehaus.org/browse/MJAVADOC-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Srb updated MJAVADOC-414: Attachment: 0002-Fix-MJAVADOC-414.patch 0001-Add-IT-for-MJAVADOC-414.patch The patch adds project's classes to javadoc's classpath, if user runs goal which produces test javadocs. IT included, based on Christian's reproducer. > Artifacts missing from test classpath. > -- > > Key: MJAVADOC-414 > URL: https://jira.codehaus.org/browse/MJAVADOC-414 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10.1 > Environment: Apache Maven 3.2.3 > (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T22:58:10+02:00) > Java version: 1.7.0_65, vendor: Oracle Corporation > Default locale: de_DE, platform encoding: UTF-8 >Reporter: Christian Schulte > Fix For: 2.10.3 > > Attachments: 0001-Add-IT-for-MJAVADOC-414.patch, > 0002-Fix-MJAVADOC-414.patch, MJAVADOC-414.patch, mjavadoc-414.zip, > mjavadoc-414.zip > > > Upgrading the javadoc plugin to version 2.10 or 2.10.1, test documentation > fails to find classpath elements from 'test' scope. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-407) Cannot parse annotations when generating javadoc
[ https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353250#comment-353250 ] Michal Srb commented on MJAVADOC-407: - Yes, that's correct and it still applies. I don't know about any case where the fix for MJAVADOC-398 causes problems. But, of course, there is always a chance that I might be missing something. I think it would be great if affected people could test the snapshot prepared by Michael and report back. Nevertheless, if Michael will decide that it will be better/safer to make MJAVADOC-398 fix optional, I am perfectly fine with it. Btw. I can prepare simple reproducer which demonstrates issue with javadoc(-plugin) and JDK8. Real world example of this issue seems to be for example this: http://mail-archives.apache.org/mod_mbox/maven-users/201409.mbox/%3CC84C4FB966D26947A3768912D36DE02A2C0ECDF7%40fgdemucimp01exc.ads.fraunhofer.de%3E > Cannot parse annotations when generating javadoc > - > > Key: MJAVADOC-407 > URL: https://jira.codehaus.org/browse/MJAVADOC-407 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: Linux and windows. > Maven 3.0.4 , JDK 1.6.0.43 >Reporter: jeff porter >Assignee: Michael Osipov > Fix For: 2.10.1 > > Attachments: AbstractJavadocMojo.java.patch > > > See full issue text at : > http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim > I'm getting the following error when I do > {noformat}mvn clean deploy -DperformRelease=true > [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist > [ERROR] import javax.inject.Named; > [ERROR] > [ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol > [ERROR] symbol: class Named > [ERROR] @Named("transactionServiceExternal") > [ERROR] > [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl > cannot be cast to com.sun.javadoc.AnnotationTypeDoc{noformat} > The POM is this... > {code:xml}com.xxx > ts-impl/artifactId> > 2.4.0-SNAPSHOT > > > javax.inject > javax.inject > 1 > > {code} > There is only one class... > {code:java}import javax.inject.Named; > @Named("transactionServiceExternal") > public class TransactionServiceExternalImpl > { > }{code} > I get the error with > jdk1.5.0_22 > jdk1.6.0_29 > jdk1.6.0_43 > jdk1.6.0_43_32bit > But NOT with... > jdk1.7.0_05 > Anyone have any ideas? > Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+) > > I now know that the reason is that the Maven Javadoc Plugin has changed from > 2.9.1 to 2.10. and this is the cause of the problem. > I can see this warning... > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING] > 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-deploy-plugin is missing. > By setting the following in my pom > org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar > I can fix the version back to the last release. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-407) cannot parse annotations : when generating javadoc
[ https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353195#comment-353195 ] Michal Srb commented on MJAVADOC-407: - @Emeric Correct, that's the line. But making it configurable is probably a good idea. javadoc tool seems to be full of surprises. > cannot parse annotations : when generating javadoc > --- > > Key: MJAVADOC-407 > URL: https://jira.codehaus.org/browse/MJAVADOC-407 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: Linux and windows. > Maven 3.0.4 , JDK 1.6.0.43 >Reporter: jeff porter >Assignee: Dennis Lundberg > Fix For: 2.10.1 > > Attachments: AbstractJavadocMojo.java.patch > > > See full issue text at : > http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim > I'm getting the following error when I do > {noformat}mvn clean deploy -DperformRelease=true > [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist > [ERROR] import javax.inject.Named; > [ERROR] > [ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol > [ERROR] symbol: class Named > [ERROR] @Named("transactionServiceExternal") > [ERROR] > [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl > cannot be cast to com.sun.javadoc.AnnotationTypeDoc{noformat} > The POM is this... > {code:xml}com.xxx > ts-impl/artifactId> > 2.4.0-SNAPSHOT > > > javax.inject > javax.inject > 1 > > {code} > There is only one class... > {code:java}import javax.inject.Named; > @Named("transactionServiceExternal") > public class TransactionServiceExternalImpl > { > }{code} > I get the error with > jdk1.5.0_22 > jdk1.6.0_29 > jdk1.6.0_43 > jdk1.6.0_43_32bit > But NOT with... > jdk1.7.0_05 > Anyone have any ideas? > Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+) > > I now know that the reason is that the Maven Javadoc Plugin has changed from > 2.9.1 to 2.10. and this is the cause of the problem. > I can see this warning... > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING] > 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-deploy-plugin is missing. > By setting the following in my pom > org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar > I can fix the version back to the last release. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-407) cannot parse annotations : when generating javadoc
[ https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353192#comment-353192 ] Michal Srb commented on MJAVADOC-407: - Hello guys, I would like to deeply apologize to everyone affected by this issue. The problem with MJAVADOC-398 is that, by some mistake, different than proposed change ended up in the Apache repository. It must have been some unfortunate mistake or glitch in some tool. Please see MJAVADOC-398 for more details. > cannot parse annotations : when generating javadoc > --- > > Key: MJAVADOC-407 > URL: https://jira.codehaus.org/browse/MJAVADOC-407 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: Linux and windows. > Maven 3.0.4 , JDK 1.6.0.43 >Reporter: jeff porter >Assignee: Dennis Lundberg > Fix For: 2.10.1 > > Attachments: AbstractJavadocMojo.java.patch > > > See full issue text at : > http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim > I'm getting the following error when I do > {noformat}mvn clean deploy -DperformRelease=true > [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist > [ERROR] import javax.inject.Named; > [ERROR] > [ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol > [ERROR] symbol: class Named > [ERROR] @Named("transactionServiceExternal") > [ERROR] > [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl > cannot be cast to com.sun.javadoc.AnnotationTypeDoc{noformat} > The POM is this... > {code:xml}com.xxx > ts-impl/artifactId> > 2.4.0-SNAPSHOT > > > javax.inject > javax.inject > 1 > > {code} > There is only one class... > {code:java}import javax.inject.Named; > @Named("transactionServiceExternal") > public class TransactionServiceExternalImpl > { > }{code} > I get the error with > jdk1.5.0_22 > jdk1.6.0_29 > jdk1.6.0_43 > jdk1.6.0_43_32bit > But NOT with... > jdk1.7.0_05 > Anyone have any ideas? > Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+) > > I now know that the reason is that the Maven Javadoc Plugin has changed from > 2.9.1 to 2.10. and this is the cause of the problem. > I can see this warning... > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING] > 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-deploy-plugin is missing. > By setting the following in my pom > org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar > I can fix the version back to the last release. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-398) Classes from build output directory can cause failure
[ https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353191#comment-353191 ] Michal Srb commented on MJAVADOC-398: - Hello guys, I would like to deeply apologize to everyone affected by this issue. I should have been more attentive. Here's what really happened: I proposed this change: https://github.com/apache/maven-plugins/pull/25/files But from some reason, different change ended up in maven-plugins repo: https://github.com/apache/maven-plugins/commit/102c98d6f519736b832deb0ae67e1a01bad1b1c0 I guess it must have been some unfortunate mistake or glitch in some tool. I am truly sorry for all the inconvenience caused by this. > Classes from build output directory can cause failure > - > > Key: MJAVADOC-398 > URL: https://jira.codehaus.org/browse/MJAVADOC-398 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: Michal Srb >Assignee: Michael Osipov > Fix For: 2.10 > > > maven-javadoc-plugin adds compiled classes from build output directory to > javadoc's classpath. There are certain cases when this can lead to either > incorrect serialized-form.html page or failure (in case of jdk8). See [1] for > more details. I think that having classes from build output directory on > javadoc's classpath is not necessary. It may cause only problems and user can > call javadoc:javadoc before actual build anyway. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1113877 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-398) Classes from build output directory can cause failure
[ https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349412#comment-349412 ] Michal Srb commented on MJAVADOC-398: - Thanks! > Classes from build output directory can cause failure > - > > Key: MJAVADOC-398 > URL: https://jira.codehaus.org/browse/MJAVADOC-398 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: Michal Srb >Assignee: Michael Osipov > Fix For: 2.9.2 > > > maven-javadoc-plugin adds compiled classes from build output directory to > javadoc's classpath. There are certain cases when this can lead to either > incorrect serialized-form.html page or failure (in case of jdk8). See [1] for > more details. I think that having classes from build output directory on > javadoc's classpath is not necessary. It may cause only problems and user can > call javadoc:javadoc before actual build anyway. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1113877 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-398) Classes from build output directory can cause failure
[ https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348855#comment-348855 ] Michal Srb commented on MJAVADOC-398: - I've opened PR on github: https://github.com/apache/maven-plugins/pull/25 > Classes from build output directory can cause failure > - > > Key: MJAVADOC-398 > URL: https://jira.codehaus.org/browse/MJAVADOC-398 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: Michal Srb > > maven-javadoc-plugin adds compiled classes from build output directory to > javadoc's classpath. There are certain cases when this can lead to either > incorrect serialized-form.html page or failure (in case of jdk8). See [1] for > more details. I think that having classes from build output directory on > javadoc's classpath is not necessary. It may cause only problems and user can > call javadoc:javadoc before actual build anyway. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1113877 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-398) Classes from build output directory can cause failure
Michal Srb created MJAVADOC-398: --- Summary: Classes from build output directory can cause failure Key: MJAVADOC-398 URL: https://jira.codehaus.org/browse/MJAVADOC-398 Project: Maven Javadoc Plugin Issue Type: Bug Affects Versions: 2.9.1 Reporter: Michal Srb maven-javadoc-plugin adds compiled classes from build output directory to javadoc's classpath. There are certain cases when this can lead to either incorrect serialized-form.html page or failure (in case of jdk8). See [1] for more details. I think that having classes from build output directory on javadoc's classpath is not necessary. It may cause only problems and user can call javadoc:javadoc before actual build anyway. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1113877 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGINTESTING-35) ClassNotFoundException: org.apache.maven.execution.MavenExecutionResult
Michal Srb created MPLUGINTESTING-35: Summary: ClassNotFoundException: org.apache.maven.execution.MavenExecutionResult Key: MPLUGINTESTING-35 URL: https://jira.codehaus.org/browse/MPLUGINTESTING-35 Project: Maven Plugin Testing Issue Type: Bug Components: plugin-testing-harness Affects Versions: 3.0.0 Environment: maven 3.1.1 Reporter: Michal Srb Attachments: maven-my-plugin.tar.gz Some important dependencies in pom.xml have scope "provided" and therefore if some project wants to use org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.0.0 it also needs to explicitly specify dependencies of plugin-testing-harness (org.apache.maven:{maven-core,maven-model,maven-aether-provider} ...). Commit 9a6269bc changed scope of all those dependencies from compile to provided, but commit message doesn't explain why. What was the reason for doing so? simple reproducer included in attachment Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira