[ https://issues.apache.org/jira/browse/MJAVADOC-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated MJAVADOC-435:
-------------------------------
Description:
Per MESOS-3482, `java` can print extra output to stderr on at launch if the `_JAVA_OPTIONS`
environment variable is set, like this:
{noformat}
tim@rocketman:temp$ _JAVA_OPTIONS=-Duser.home=/tmp java -version
Picked up _JAVA_OPTIONS: -Duser.home=/tmp
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
{noformat}
This plugin attempts to parse stderr to learn the javadoc version and does not expect the
additional output.
The failure looks like:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:48 min
[INFO] Finished at: 2015-09-21T15:24:14+01:00
[INFO] Final Memory: 29M/242M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:jar (build-and-attach-javadocs)
on project mesos: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - Picked up _JAVA_OPTIONS: -Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
[ERROR] javadoc: error - No packages or classes specified.
[ERROR]
[ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/javadoc
@options
{noformat}
I think this should work even in the presence of _JAVA_OPTIONS.
Homebrew is considering setting this variable widely (tracking at https://github.com/Homebrew/homebrew/pull/44567)
which would cause build problems for maven projects that use this plugin.
was:
Per MESOS-3482, `java` can print extra output to stderr on at launch if the `_JAVA_OPTIONS`
environment variable is set, like this:
```
tim@rocketman:temp$ _JAVA_OPTIONS=-Duser.home=/tmp java -version
Picked up _JAVA_OPTIONS: -Duser.home=/tmp
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
```
This plugin attempts to parse stderr to learn the javadoc version and does not expect the
additional output.
The failure looks like:
```
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:48 min
[INFO] Finished at: 2015-09-21T15:24:14+01:00
[INFO] Final Memory: 29M/242M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:jar (build-and-attach-javadocs)
on project mesos: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - Picked up _JAVA_OPTIONS: -Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
[ERROR] javadoc: error - No packages or classes specified.
[ERROR]
[ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/javadoc
@options
```
I think this should work even in the presence of _JAVA_OPTIONS.
Homebrew is considering setting this variable widely (tracking at https://github.com/Homebrew/homebrew/pull/44567)
which would cause build problems for maven projects that use this plugin.
> _JAVA_OPTIONS interferes with javadoc version detection
> -------------------------------------------------------
>
> Key: MJAVADOC-435
> URL: https://issues.apache.org/jira/browse/MJAVADOC-435
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Reporter: Tim Smith
>
> Per MESOS-3482, `java` can print extra output to stderr on at launch if the `_JAVA_OPTIONS`
environment variable is set, like this:
> {noformat}
> tim@rocketman:temp$ _JAVA_OPTIONS=-Duser.home=/tmp java -version
> Picked up _JAVA_OPTIONS: -Duser.home=/tmp
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> {noformat}
> This plugin attempts to parse stderr to learn the javadoc version and does not expect
the additional output.
> The failure looks like:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 02:48 min
> [INFO] Finished at: 2015-09-21T15:24:14+01:00
> [INFO] Final Memory: 29M/242M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:jar
(build-and-attach-javadocs) on project mesos: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - Picked up _JAVA_OPTIONS: -Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
> [ERROR] javadoc: error - No packages or classes specified.
> [ERROR]
> [ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/javadoc
@options
> {noformat}
> I think this should work even in the presence of _JAVA_OPTIONS.
> Homebrew is considering setting this variable widely (tracking at https://github.com/Homebrew/homebrew/pull/44567)
which would cause build problems for maven projects that use this plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|