Build unstable in Jenkins: Maven TLP » maven-javadoc-plugin » master #3

[Apache Jenkins Server]

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/3/

Changes:

* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* [maven-release-plugin] prepare release maven-javadoc-plugin-3.0.0
* [maven-release-plugin] prepare for next development iteration
* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* [maven-release-plugin] prepare release maven-javadoc-plugin-3.0.0
* [maven-release-plugin] prepare for next development iteration
* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* [maven-release-plugin] prepare release maven-javadoc-plugin-3.0.0
* [maven-release-plugin] prepare for next development iteration
* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* [maven-release-plugin] prepare release maven-javadoc-plugin-3.0.0
* [maven-release-plugin] prepare for next development iteration
* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* [maven-release-plugin] prepare release maven-javadoc-plugin-3.0.0
* [maven-release-plugin] prepare for next development iteration
* Switch from List to Collection to make it easier to use Sets when
* Group sets of sourcepaths per project, in prepare of usage of
* Add project/artifact key to set of sourcePaths to recognize reactor
* session is required parameter, so cannot be null. Fix related unittests
* MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
* unittest should prefer JAVA_HOME when executing from cmdline When
* Improve TestJavadocReportTest#testTestJavadoc J8 warns and continues
* Upgrade mockito to remove warning about illegal reflective access
* JDK-8032205 was closed as not an issue, so not solved in Java9. Need to
* Skip several unittests for Java9
* [MJAVADOC-498] "module not found" when Java 9 module-info present
* 

Build unstable in Jenkins: Maven TLP » maven-javadoc-plugin » master #2

[Apache Jenkins Server]

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/2/

Changes:

* Noting INFRA-15651
* Typowq
* [MJAVADOC-508] option to fail the build in case of javadoc warnings
* [MJAVADOC-508] add it test and fix bloody checkstyle :-)
* [MJAVADOC-508] option to fail the build in case of javadoc warnings
* [MJAVADOC-508] add it test and fix bloody checkstyle :-)
* [MJAVADOC-508] option to fail the build in case of javadoc warnings
* [MJAVADOC-508] add it test and fix bloody checkstyle :-)
* [MJAVADOC-508] option to fail the build in case of javadoc warnings
* [MJAVADOC-508] add it test and fix bloody checkstyle :-)

17 tests failed.
FAILED:  org.apache.maven.plugins.javadoc.JavadocReportTest.testJavadocResources

Error Message:
This bug appeared in JDK8 and was planned to be fixed in JDK9, see JDK-8032205

Stack Trace:
junit.framework.AssertionFailedError: This bug appeared in JDK8 and was planned 
to be fixed in JDK9, see JDK-8032205
at 
org.apache.maven.plugins.javadoc.JavadocReportTest.testJavadocResources(JavadocReportTest.java:637)


FAILED:  org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFix

Error Message:
Error occurred during initialization of VM, try to reduce the Java heap size 
for the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.

Stack Trace:
org.apache.maven.shared.invoker.MavenInvocationException: Error occurred during 
initialization of VM, try to reduce the Java heap size for the MAVEN_OPTS 
environnement variable using -Xms: and -Xmx:.
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.invokeCompileGoal(FixJavadocMojoTest.java:655)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.executeMojoAndTest(FixJavadocMojoTest.java:612)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFix(FixJavadocMojoTest.java:141)


FAILED:  org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk5

Error Message:
Error occurred during initialization of VM, try to reduce the Java heap size 
for the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.

Stack Trace:
org.apache.maven.shared.invoker.MavenInvocationException: Error occurred during 
initialization of VM, try to reduce the Java heap size for the MAVEN_OPTS 
environnement variable using -Xms: and -Xmx:.
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.invokeCompileGoal(FixJavadocMojoTest.java:655)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.executeMojoAndTest(FixJavadocMojoTest.java:612)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk5(FixJavadocMojoTest.java:152)


FAILED:  org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk6

Error Message:
Error occurred during initialization of VM, try to reduce the Java heap size 
for the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.

Stack Trace:
org.apache.maven.shared.invoker.MavenInvocationException: Error occurred during 
initialization of VM, try to reduce the Java heap size for the MAVEN_OPTS 
environnement variable using -Xms: and -Xmx:.
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.invokeCompileGoal(FixJavadocMojoTest.java:655)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.executeMojoAndTest(FixJavadocMojoTest.java:612)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk6(FixJavadocMojoTest.java:163)


FAILED:  org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFix

Error Message:
Error occurred during initialization of VM, try to reduce the Java heap size 
for the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.

Stack Trace:
org.apache.maven.shared.invoker.MavenInvocationException: Error occurred during 
initialization of VM, try to reduce the Java heap size for the MAVEN_OPTS 
environnement variable using -Xms: and -Xmx:.
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.invokeCompileGoal(FixJavadocMojoTest.java:655)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.executeMojoAndTest(FixJavadocMojoTest.java:612)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFix(FixJavadocMojoTest.java:141)


FAILED:  org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk5

Error Message:
Error occurred during initialization of VM, try to reduce the Java heap size 
for the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.

Stack Trace:
org.apache.maven.shared.invoker.MavenInvocationException: Error occurred during 
initialization of VM, try to reduce the Java heap size for the MAVEN_OPTS 
environnement variable using -Xms: and -Xmx:.
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.invokeCompileGoal(FixJavadocMojoTest.java:655)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.executeMojoAndTest(FixJavadocMojoTest.java:612)
at 
org.apache.maven.plugins.javadoc.FixJavadocMojoTest.testFixJdk5(FixJavadocMojoTest.java:152)


FAILED:  

Build succeeded in Jenkins: maven-3.x-jenkinsfile » master #150

[Apache Jenkins Server]

See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/150/

Changes:

* [MNG-6330] Parents relativePath not verified anymore
* [MNG-6308] make IT more tolerant on format change
* [MNG-6330] Parents relativePath not verified anymore
* [MNG-6308] make IT more tolerant on format change
* [MNG-6330] Parents relativePath not verified anymore
* [MNG-6308] make IT more tolerant on format change
* [MNG-6330] Parents relativePath not verified anymore
* [MNG-6308] make IT more tolerant on format change
* [MNG-6330] Parents relativePath not verified anymore

All tests passed

[PING] The GIT master branch of Maven has unreleased changes that do not pass Shared Components integration tests on Windows

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing Shared Components integration tests on Windows.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

maven-3.x-site - Build # 1077 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built maven-3.x-site (build #1077)

Status: Still Failing

Check console output at https://builds.apache.org/job/maven-3.x-site/1077/ to 
view the results.

[PING] The GIT master branch of Maven has unreleased changes that do not pass plugin integration tests on Windows

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing plugin integration tests on Windows.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass Shared Components integration tests on Linux

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing Shared Components integration tests on Linux.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass plugin integration tests on Linux

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing plugin integration tests on Linux.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass a resolver build on Windows including integration tests.

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing a resolver build on Windows including integration tests.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass a resolver build including integration tests on Linux

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing a resolver build on Linux including integration tests.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass core integration tests on Linux

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passsing core integration tests on Linux.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

[PING] The GIT master branch of Maven has unreleased changes that do not pass JXR integration tests on Linux

[Apache Jenkins Server]

This is an automated email to notify the Maven developer list that there are 
unreleased changes in the GIT master branch of Maven that have passed a release 
build not passing JXR integration tests on Linux.



Please review the following build job for any issues with changes to the Maven 
master branch.



-Jenkins

maven-3.x - Build # 1685 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built maven-3.x (build #1685)

Status: Still Failing

Check console output at https://builds.apache.org/job/maven-3.x/1685/ to view 
the results.

maven-3.x - Build # 1684 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built maven-3.x (build #1684)

Status: Failure

Check console output at https://builds.apache.org/job/maven-3.x/1684/ to view 
the results.