[jira] [Created] (MNG-6523) System Dependencies Deprication

[Alireza Fattahi (JIRA)]

Alireza Fattahi created MNG-6523:


 Summary: System Dependencies Deprication
 Key: MNG-6523
 URL: https://issues.apache.org/jira/browse/MNG-6523
 Project: Maven
  Issue Type: Wish
Reporter: Alireza Fattahi


Please let me know if this is wrong place for discussions about this.

As mentioned in 
[https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#System_Dependencies]
 the System Dependencies will be depreciated and should not be used.

Well this feature seems very useful in some cases and must developers find it 
easy to use:

[https://stackoverflow.com/a/4491469/2648077]
 [https://stackoverflow.com/a/22300875/2648077]

 

Well I wish it wouldn't be deprecated at all :)

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6261) Relative parent POM resolution failing in 3.5.0 with complex multimodule builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692426#comment-16692426
 ] 

ASF GitHub Bot commented on MNG-6261:
-

fabcipriano commented on issue #192: [MNG-6261] - using java File api to compare
URL: https://github.com/apache/maven/pull/192#issuecomment-440080853
 
 
   > 
   > 
   > Looks also good according to 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6261/
   > Can you add yourself as contributor to the pom.xml and squash the commits?
   
   Done.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Relative parent POM resolution failing in 3.5.0 with complex multimodule 
> builds
> ---
>
> Key: MNG-6261
> URL: https://issues.apache.org/jira/browse/MNG-6261
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Dawid Weiss
>Priority: Minor
>  Labels: up-for-grabs
> Fix For: 3.6.x-candidate
>
> Attachments: capture-6.png, repro.zip
>
>
> In my effort to upgrade an existing (fairly complex) Maven build to Java 
> 1.9.0 I updated Maven to 3.5.0 (from 3.3.9). Unfortunately I get errors when 
> the project's modules are resolved:
> {noformat}
> > mvn validate
> [FATAL] Non-resolvable parent POM for 
> com.carrotsearch.lingo4g:lingo4g-public-bom:[unknown-version]: Could not find 
> artifact com.carrotsearch.lingo4g:lingo4g-public:pom:1.6.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 5, column 11
> ...
> (and many follow).
> {noformat}
> This build has a correct pom parent-structure (a tree), but is fairly complex 
> -- the submodule hierarchy is not aligned with parent-child pom hierarchy 
> (it's best to look at the repro code to understand how it's structured).
> However, it's been working correctly with all prior Maven versions and I 
> wonder if it's a regression bug or maybe underspecified Maven requirement 
> (that should be enforced with a warning and not lead to this odd runtime 
> message).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] fabcipriano commented on issue #192: [MNG-6261] - using java File api to compare

[GitBox]

fabcipriano commented on issue #192: [MNG-6261] - using java File api to compare
URL: https://github.com/apache/maven/pull/192#issuecomment-440080853
 
 
   > 
   > 
   > Looks also good according to 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6261/
   > Can you add yourself as contributor to the pom.xml and squash the commits?
   
   Done.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MNG-6522) Prepare Maven's Core Integration Test Suite to test with Java 12-ea

[Sylwester Lachiewicz (JIRA)]

Sylwester Lachiewicz created MNG-6522:
-

 Summary: Prepare Maven's Core Integration Test Suite to test with 
Java 12-ea
 Key: MNG-6522
 URL: https://issues.apache.org/jira/browse/MNG-6522
 Project: Maven
  Issue Type: Improvement
  Components: Integration Tests
Reporter: Sylwester Lachiewicz






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692257#comment-16692257
 ] 

Hudson commented on MJAVADOC-538:
-

Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » master #69

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

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: EXTERNAL: [jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Daly, Jeff]

UNSUBSCRIBE

-Original Message-
From: Robert Scholte (JIRA)  
Sent: Monday, November 19, 2018 3:40 PM
To: issues@maven.apache.org
Subject: EXTERNAL: [jira] [Issue Comment Deleted] (MJAVADOC-538) JVM 
"JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, 
triggers failure


 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on a change in pull request #11: [MJAVADOC-538] 
Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234453033
 
 

 ##
 File path: pom.xml
 ##
 @@ -441,6 +441,7 @@ under the License.
   
   
 
true
+<_JAVA_OPTIONS>-Dabc=def
 
 Review comment:
   Please add a comment behind it like this: ``


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the URL above to go to 
the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure
> --
> ---
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 
> 64-Bit Server VM (build 25.181-b13, mixed mode){noformat} Apparently 
> this message cannot be suppressed, that's on purpose an won't change: 
> [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork 
> (generate-javadoc) @ hibernate-search-util-internal-common --- [INFO] The 
> goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' has not 
> been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated 
> invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/t
> est/target/site/apidocs [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo {noformat} (see the last 
> line, the message appears in the list of warnings) No big deal... 
> until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439978885
 
 
   One final request: add yourself as contributor to the root `pom.xml` if you 
want.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6261) Relative parent POM resolution failing in 3.5.0 with complex multimodule builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692244#comment-16692244
 ] 

ASF GitHub Bot commented on MNG-6261:
-

rfscholte commented on issue #192: [MNG-6261] - using java File api to compare
URL: https://github.com/apache/maven/pull/192#issuecomment-440035852
 
 
   Looks also good according to 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6261/
   Can you add yourself as contributor to the pom.xml and squash the commits? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Relative parent POM resolution failing in 3.5.0 with complex multimodule 
> builds
> ---
>
> Key: MNG-6261
> URL: https://issues.apache.org/jira/browse/MNG-6261
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Dawid Weiss
>Priority: Minor
>  Labels: up-for-grabs
> Fix For: 3.6.x-candidate
>
> Attachments: capture-6.png, repro.zip
>
>
> In my effort to upgrade an existing (fairly complex) Maven build to Java 
> 1.9.0 I updated Maven to 3.5.0 (from 3.3.9). Unfortunately I get errors when 
> the project's modules are resolved:
> {noformat}
> > mvn validate
> [FATAL] Non-resolvable parent POM for 
> com.carrotsearch.lingo4g:lingo4g-public-bom:[unknown-version]: Could not find 
> artifact com.carrotsearch.lingo4g:lingo4g-public:pom:1.6.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 5, column 11
> ...
> (and many follow).
> {noformat}
> This build has a correct pom parent-structure (a tree), but is fairly complex 
> -- the submodule hierarchy is not aligned with parent-child pom hierarchy 
> (it's best to look at the repro code to understand how it's structured).
> However, it's been working correctly with all prior Maven versions and I 
> wonder if it's a regression bug or maybe underspecified Maven requirement 
> (that should be enforced with a warning and not lead to this odd runtime 
> message).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] rfscholte commented on issue #192: [MNG-6261] - using java File api to compare

[GitBox]

rfscholte commented on issue #192: [MNG-6261] - using java File api to compare
URL: https://github.com/apache/maven/pull/192#issuecomment-440035852
 
 
   Looks also good according to 
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6261/
   Can you add yourself as contributor to the pom.xml and squash the commits? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk opened a new pull request #11: [MJAVADOC-538] Filter out 'Picked 
up'
URL: https://github.com/apache/maven-javadoc-plugin/pull/11
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte closed pull request #11: [MJAVADOC-538] Filter out 'Picked up'
URL: https://github.com/apache/maven-javadoc-plugin/pull/11
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index fa19d3e..cd6cc3b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -113,6 +113,9 @@ under the License.
 
   Anton Klarén
 
+
+  Kevin Risden
+
   
 
   
@@ -441,6 +444,8 @@ under the License.
   
   
 
true
+
+<_JAVA_OPTIONS>-Dabc=def
   
 
   
diff --git a/src/it/projects/MJAVADOC-538/invoker.properties 
b/src/it/projects/MJAVADOC-538/invoker.properties
new file mode 100644
index 000..a4e250d
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/invoker.properties
@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+invoker.goals=clean javadoc:javadoc
diff --git a/src/it/projects/MJAVADOC-538/pom.xml 
b/src/it/projects/MJAVADOC-538/pom.xml
new file mode 100644
index 000..e7d3ae1
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/pom.xml
@@ -0,0 +1,48 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+  https://issues.apache.org/jira/browse/MJAVADOC-538
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @project.version@
+  
+true
+  
+
+  
+
+  
+
diff --git a/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java 
b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
new file mode 100644
index 000..e5960e3
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
@@ -0,0 +1,24 @@
+package foo.bar;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ * 
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+public class MyClass
+{
+}
diff --git 
a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java 
b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
index e19b68f..5dc3fd6 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
@@ -5251,8 +5251,8 @@ private void executeJavadocCommandLine( Commandline cmd, 
File javadocOutputDirec
 writeDebugJavadocScript( cmdLine, javadocOutputDirectory );
 }
 
-CommandLineUtils.StringStreamConsumer err = new 
CommandLineUtils.StringStreamConsumer();
-CommandLineUtils.StringStreamConsumer out = new 
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.StringStreamConsumer err = new 
JavadocUtil.JavadocOutputStreamConsumer();
+CommandLineUtils.StringStreamConsumer out = new 

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: yrodiere commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-438566431
 
 
   FWIW, I can confirm this solves the problem in my project. Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439982524
 
 
   @rfscholte added myself as contributor. Let me know if there is anything 
else :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter 
out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629612
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter 
out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629528
 
 

 ##
 File path: pom.xml
 ##
 @@ -441,6 +441,7 @@ under the License.
   
   
 
true
+<_JAVA_OPTIONS>-Dabc=def
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter 
out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629709
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @pom.version@
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on a change in pull request #11: [MJAVADOC-538] 
Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234453162
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @pom.version@
+
 
 Review comment:
   As said, put the fialOnWarning here as configuration (and I'd prefer 
project.version over pom.version)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439904246
 
 
   @rfscholte Addressed your review comments. Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on a change in pull request #11: [MJAVADOC-538] 
Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234453124
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
 
 Review comment:
   Add `https://issues.apache.org/jira/browse/MJAVADOC-538` for easy 
access to original issue


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on a change in pull request #11: [MJAVADOC-538] 
Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234453156
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/invoker.properties
 ##
 @@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+invoker.goals=clean javadoc:javadoc -Dmaven.javadoc.failOnWarnings=true
 
 Review comment:
   Make the property explicit in the plugin configuration, otherwise it could 
be overwritten from commandline when executing integration tests.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> 

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439667626
 
 
   Added integration test.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-440016371
 
 
   
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-538/
   I need to figure out what's wrong with Windows + Java 7 before merging 
(looks unrelated to this commit)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJAVADOC-538:

Comment: was deleted

(was: rfscholte commented on a change in pull request #11: [MJAVADOC-538] 
Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234453033
 
 

 ##
 File path: pom.xml
 ##
 @@ -441,6 +441,7 @@ under the License.
   
   
 
true
+<_JAVA_OPTIONS>-Dabc=def
 
 Review comment:
   Please add a comment behind it like this: ``


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692227#comment-16692227
 ] 

Robert Scholte commented on MJAVADOC-538:
-

Fixed in 
[631a84ee0a54acc916b0958b9c5b86a5d417712d|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=631a84ee0a54acc916b0958b9c5b86a5d417712d]
Thanks for the patch!

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MJAVADOC-538.
---
   Resolution: Fixed
 Assignee: Robert Scholte
Fix Version/s: 3.0.2

> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.2
>
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692225#comment-16692225
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

rfscholte closed pull request #11: [MJAVADOC-538] Filter out 'Picked up'
URL: https://github.com/apache/maven-javadoc-plugin/pull/11
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index fa19d3e..cd6cc3b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -113,6 +113,9 @@ under the License.
 
   Anton Klarén
 
+
+  Kevin Risden
+
   
 
   
@@ -441,6 +444,8 @@ under the License.
   
   
 
true
+
+<_JAVA_OPTIONS>-Dabc=def
   
 
   
diff --git a/src/it/projects/MJAVADOC-538/invoker.properties 
b/src/it/projects/MJAVADOC-538/invoker.properties
new file mode 100644
index 000..a4e250d
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/invoker.properties
@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+invoker.goals=clean javadoc:javadoc
diff --git a/src/it/projects/MJAVADOC-538/pom.xml 
b/src/it/projects/MJAVADOC-538/pom.xml
new file mode 100644
index 000..e7d3ae1
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/pom.xml
@@ -0,0 +1,48 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+  https://issues.apache.org/jira/browse/MJAVADOC-538
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @project.version@
+  
+true
+  
+
+  
+
+  
+
diff --git a/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java 
b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
new file mode 100644
index 000..e5960e3
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
@@ -0,0 +1,24 @@
+package foo.bar;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ * 
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+public class MyClass
+{
+}
diff --git 
a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java 
b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
index e19b68f..5dc3fd6 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
@@ -5251,8 +5251,8 @@ private void executeJavadocCommandLine( Commandline cmd, 
File javadocOutputDirec
 writeDebugJavadocScript( cmdLine, javadocOutputDirectory );
 }
 
-CommandLineUtils.StringStreamConsumer err = new 
CommandLineUtils.StringStreamConsumer();
-CommandLineUtils.StringStreamConsumer out = new 
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.StringStreamConsumer err = new 
JavadocUtil.JavadocOutputStreamConsumer();
+CommandLineUtils.StringStreamConsumer out = new 

[GitHub] rfscholte closed pull request #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

rfscholte closed pull request #11: [MJAVADOC-538] Filter out 'Picked up'
URL: https://github.com/apache/maven-javadoc-plugin/pull/11
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index fa19d3e..cd6cc3b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -113,6 +113,9 @@ under the License.
 
   Anton Klarén
 
+
+  Kevin Risden
+
   
 
   
@@ -441,6 +444,8 @@ under the License.
   
   
 
true
+
+<_JAVA_OPTIONS>-Dabc=def
   
 
   
diff --git a/src/it/projects/MJAVADOC-538/invoker.properties 
b/src/it/projects/MJAVADOC-538/invoker.properties
new file mode 100644
index 000..a4e250d
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/invoker.properties
@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+invoker.goals=clean javadoc:javadoc
diff --git a/src/it/projects/MJAVADOC-538/pom.xml 
b/src/it/projects/MJAVADOC-538/pom.xml
new file mode 100644
index 000..e7d3ae1
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/pom.xml
@@ -0,0 +1,48 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+  https://issues.apache.org/jira/browse/MJAVADOC-538
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @project.version@
+  
+true
+  
+
+  
+
+  
+
diff --git a/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java 
b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
new file mode 100644
index 000..e5960e3
--- /dev/null
+++ b/src/it/projects/MJAVADOC-538/src/main/java/foo/bar/MyClass.java
@@ -0,0 +1,24 @@
+package foo.bar;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ * 
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+public class MyClass
+{
+}
diff --git 
a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java 
b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
index e19b68f..5dc3fd6 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
@@ -5251,8 +5251,8 @@ private void executeJavadocCommandLine( Commandline cmd, 
File javadocOutputDirec
 writeDebugJavadocScript( cmdLine, javadocOutputDirectory );
 }
 
-CommandLineUtils.StringStreamConsumer err = new 
CommandLineUtils.StringStreamConsumer();
-CommandLineUtils.StringStreamConsumer out = new 
CommandLineUtils.StringStreamConsumer();
+CommandLineUtils.StringStreamConsumer err = new 
JavadocUtil.JavadocOutputStreamConsumer();
+CommandLineUtils.StringStreamConsumer out = new 
JavadocUtil.JavadocOutputStreamConsumer();
 try
 {
 int exitCode = CommandLineUtils.executeCommandLine( cmd, out, err 
);
diff --git a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java 

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692157#comment-16692157
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-440016371
 
 
   
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-538/
   I need to figure out what's wrong with Windows + Java 7 before merging 
(looks unrelated to this commit)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-440016371
 
 
   
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-538/
   I need to figure out what's wrong with Windows + Java 7 before merging 
(looks unrelated to this commit)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692058#comment-16692058
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439982524
 
 
   @rfscholte added myself as contributor. Let me know if there is anything 
else :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439982524
 
 
   @rfscholte added myself as contributor. Let me know if there is anything 
else :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692048#comment-16692048
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439978885
 
 
   One final request: add yourself as contributor to the root `pom.xml` if you 
want.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

rfscholte commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439978885
 
 
   One final request: add yourself as contributor to the root `pom.xml` if you 
want.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAR-260) Warn about invalid 'Automatic-Module-Name' in MANIFEST

[Christian Stein (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692030#comment-16692030
 ] 

Christian Stein commented on MJAR-260:
--

Updated related PR to use Archiver 3.3.0 (from staged repo) ... it still 
contains the two new integration tests.

> Warn about invalid 'Automatic-Module-Name' in MANIFEST
> --
>
> Key: MJAR-260
> URL: https://issues.apache.org/jira/browse/MJAR-260
> Project: Maven JAR Plugin
>  Issue Type: Improvement
>Reporter: Christian Stein
>Assignee: Christian Stein
>Priority: Minor
> Fix For: 3.1.1
>
>
> The Maven JAR Plugin should warn or even fail when an invalid name is 
> detected within the `META-INF/MANIFEST.MF` file.
> For details see 
> https://sormuras.github.io/blog/2018-11-16-invalid-automatic-module-names



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6521) remove deprecated main attributes from generated MANIFEST

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691964#comment-16691964
 ] 

Michael Osipov commented on MNG-6521:
-

Interesting, but the attributes aren't read through code anymore. They are 
solely for humans, aren't they? It does not hurt to have them by now, does it?

> remove deprecated main attributes from generated MANIFEST
> -
>
> Key: MNG-6521
> URL: https://issues.apache.org/jira/browse/MNG-6521
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.6.0
>Reporter: Franz van Betteraey
>Priority: Minor
>
> The MANIFEST implementation entries can be generated by using the 
> 'addDefaultImplementationEntries' of the Apache Maven Archiver configuration
> (http://maven.apache.org/shared/maven-archiver/index.html#class_manifest) 
> like this:
>     
>     
>     
> true
>     
>     
>     
> This will add
>     Implementation-Title: ${project.name}
>     Implementation-Version: ${project.version}
>     Implementation-Vendor-Id: ${project.groupId}
>     Implementation-Vendor: ${project.organization.name}
>     Implementation-URL: ${project.url}
> to the MANIFEST.MF file. But
>     Implementation-Vendor-Id and
>     Implementation-URL
> are deprecated by now (at least since Java 8 as seen here): 
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#Main_Attributes
> In the Java 11 jar Manifest Specification they are not mentioned anymore.
> https://docs.oracle.com/en/java/javase/11/docs/specs/jar/jar.html#manifest-specification
> Thus I guess they also should be removed while generating the main 
> implementation entries by the Maven Archiver.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1593) 3.0.0-M1 produces invalid code sources on Windows

[Jesse Glick (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691868#comment-16691868
 ] 

Jesse Glick commented on SUREFIRE-1593:
---

[Final 
fix|https://github.com/apache/maven-surefire/commit/f5cca5bcc2c85060c21c82eea0081d016cb86909]

> 3.0.0-M1 produces invalid code sources on Windows
> -
>
> Key: SUREFIRE-1593
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1593
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: classloading, process forking
>Affects Versions: 3.0.0-M1
>Reporter: Jesse Glick
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M2
>
>
> The fix for SUREFIRE-1588 did not work correctly on Windows. (When 
> active—i.e., when the drive letters of the system temporary directory, per 
> SUREFIRE-1400, and the project basedir were the same.) It would produce 
> relative URIs containing {{%5C}} where {{/}} was intended.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MNG-6521) remove deprecated main attributes from generated MANIFEST

[Franz van Betteraey (JIRA)]

Franz van Betteraey created MNG-6521:


 Summary: remove deprecated main attributes from generated MANIFEST
 Key: MNG-6521
 URL: https://issues.apache.org/jira/browse/MNG-6521
 Project: Maven
  Issue Type: Improvement
  Components: Artifacts and Repositories
Affects Versions: 3.6.0
Reporter: Franz van Betteraey


The MANIFEST implementation entries can be generated by using the 
'addDefaultImplementationEntries' of the Apache Maven Archiver configuration
(http://maven.apache.org/shared/maven-archiver/index.html#class_manifest) like 
this:

    
    
    
true
    
    
    
This will add

    Implementation-Title: ${project.name}
    Implementation-Version: ${project.version}
    Implementation-Vendor-Id: ${project.groupId}
    Implementation-Vendor: ${project.organization.name}
    Implementation-URL: ${project.url}

to the MANIFEST.MF file. But

    Implementation-Vendor-Id and
    Implementation-URL

are deprecated by now (at least since Java 8 as seen here): 
https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#Main_Attributes

In the Java 11 jar Manifest Specification they are not mentioned anymore.
https://docs.oracle.com/en/java/javase/11/docs/specs/jar/jar.html#manifest-specification

Thus I guess they also should be removed while generating the main 
implementation entries by the Maven Archiver.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691735#comment-16691735
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629528
 
 

 ##
 File path: pom.xml
 ##
 @@ -441,6 +441,7 @@ under the License.
   
   
 
true
+<_JAVA_OPTIONS>-Dabc=def
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691737#comment-16691737
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439904246
 
 
   @rfscholte Addressed your review comments. Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691734#comment-16691734
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629709
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @pom.version@
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

risdenk commented on issue #11: [MJAVADOC-538] Filter out 'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#issuecomment-439904246
 
 
   @rfscholte Addressed your review comments. Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-538) JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691733#comment-16691733
 ] 

ASF GitHub Bot commented on MJAVADOC-538:
-

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629612
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc 
> warning, triggers failure 
> -
>
> Key: MJAVADOC-538
> URL: https://issues.apache.org/jira/browse/MJAVADOC-538
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Maven 3.5.4
> Java 1.8.0_181
>Reporter: Yoann Rodière
>Priority: Major
>
> When an environment variable {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is 
> defined, every JVM that starts will output a message to inform users of these 
> options being picked up:
> {noformat}
> $ export JAVA_TOOL_OPTIONS=-Dfoo
> $ java -version     
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode){noformat}
> Apparently this message cannot be suppressed, that's on purpose an won't 
> change: [https://bugs.openjdk.java.net/browse/JDK-8039152]
>  
> Unfortunately, this message seems to be interpreted by the 
> maven-javadoc-plugin as a warning:
> {noformat}
> [INFO] --- maven-javadoc-plugin:3.0.1:javadoc-no-fork (generate-javadoc) @ 
> hibernate-search-util-internal-common ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc' 
> has not been previously called for the module: 
> 'org.hibernate.search:hibernate-search-util-internal-test:jar:6.0.0-SNAPSHOT'.
>  Trying to invoke it...
> [WARN] Maven will be executed in interactive mode, but no input stream has 
> been configured for this MavenInvoker instance.
> Picked up JAVA_TOOL_OPTIONS: -Dfoo
> [WARNING] Creating fake javadoc directory to prevent repeated invocations: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs
> [ERROR] Error fetching link: 
> /home/yrodiere/workspaces/main/hibernate-search-parent/util/internal/test/target/site/apidocs/package-list.
>  Ignored it.
> [WARNING] Javadoc Warnings
> [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dfoo
> {noformat}
> (see the last line, the message appears in the list of warnings)
> No big deal... until you enable the 
> [failOnWarnings|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#failOnWarnings]
>  option. Then the whole build will fail just because some JVM detected an 
> environment variable...
> I couldn't find any workaround, except disabling the {{failOnWarnings}} 
> options, but that's more a surrender than a workaround.
> Note that the definition of {{_JAVA_OPTIONS}} or {{JAVA_TOOL_OPTIONS}} is not 
> exactly an exotic use case, especially on Continuous Integration platforms. 
> [Travis CI uses {{_JAVA_OPTIONS}} 
> |https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/#added] 
> to set JVM memory limits in its containerized environments, and [the Jenkins 
> CI Pipeline Maven plugin uses 
> {{JAVA_TOOL_OPTIONS}}|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22[WARNING]PickedupJAVA_TOOL_OPTIONS...%22inthebuildlogs?]
>  to pass options to Maven processes transparently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629528
 
 

 ##
 File path: pom.xml
 ##
 @@ -441,6 +441,7 @@ under the License.
   
   
 
true
+<_JAVA_OPTIONS>-Dabc=def
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629612
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 'Picked up'

[GitBox]

risdenk commented on a change in pull request #11: [MJAVADOC-538] Filter out 
'Picked up'
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/11#discussion_r234629709
 
 

 ##
 File path: src/it/projects/MJAVADOC-538/pom.xml
 ##
 @@ -0,0 +1,44 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  org.apache.maven.plugins.maven-javadoc-plugin.it
+  mjavadoc-538
+  1.0-SNAPSHOT
+
+  
+UTF-8
+  
+
+  
+
+  
+
+  org.apache.maven.plugins
+  maven-javadoc-plugin
+  @pom.version@
+
 
 Review comment:
   Added.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Updated] (SUREFIRE-1601) Cannot run JUnit test under OpenJDK 11: The forked VM terminated without properly saying goodbye

[Thorsten Heit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thorsten Heit updated SUREFIRE-1601:

Description: 
I tried to execute "mvn clean install" on our build server for a project that 
contains a few JUnit 4 tests. When I use OpenJDK 11, m-surefire-p doesn't work:
{noformat}
(...)
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M1:test (default-test) @ myjob ---
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 
1. See FAQ web page and the dump file 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports/2018-11-19T08-44-36_188-jvmRun1.dumpstream
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  7.042 s
[INFO] Finished at: 2018-11-19T08:44:36+01:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test (default-test) on 
project myjob: There are test failures.
[ERROR]
[ERROR] Please refer to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports
 for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, 
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:283)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1149)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:991)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:837)
[ERROR] at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)

[jira] [Updated] (SUREFIRE-1601) Cannot run JUnit test under OpenJDK 11: The forked VM terminated without properly saying goodbye

[Thorsten Heit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thorsten Heit updated SUREFIRE-1601:

Description: 
I tried to execute "mvn clean install" on our build server for a project that 
contains a few JUnit 4 tests. When I use OpenJDK 11, m-surefire-p doesn't work:
{noformat}
(...)
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M1:test (default-test) @ myjob ---
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 
1. See FAQ web page and the dump file 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports/2018-11-19T08-44-36_188-jvmRun1.dumpstream
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  7.042 s
[INFO] Finished at: 2018-11-19T08:44:36+01:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test (default-test) on 
project myjob: There are test failures.
[ERROR]
[ERROR] Please refer to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports
 for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, 
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:283)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1149)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:991)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:837)
[ERROR] at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)

[jira] [Created] (SUREFIRE-1601) Cannot run JUnit test under OpenJDK 11: The forked VM terminated without properly saying goodbye

[Thorsten Heit (JIRA)]

Thorsten Heit created SUREFIRE-1601:
---

 Summary: Cannot run JUnit test under OpenJDK 11: The forked VM 
terminated without properly saying goodbye
 Key: SUREFIRE-1601
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1601
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M1
 Environment: * Linux Debian Testing x64
* openjdk version "10.0.2" 2018-07-17
  OpenJDK Runtime Environment (build 10.0.2+13-Debian-2)
  OpenJDK 64-Bit Server VM (build 10.0.2+13-Debian-2, mixed mode)
* openjdk version "11.0.1" 2018-10-16
  OpenJDK Runtime Environment (build 11.0.1+13-Debian-2)
  OpenJDK 64-Bit Server VM (build 11.0.1+13-Debian-2, mixed mode, sharing)
* Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T20:41:47+02:00)
Reporter: Thorsten Heit


I tried to execute "mvn clean install" on our build server for a project that 
contains a few JUnit 4 tests. When I use OpenJDK for Maven (3.6.0, btw), 
m-surefire-p doesn't work:
{noformat}
(...)
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M1:test (default-test) @ myjob ---
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 
1. See FAQ web page and the dump file 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports/2018-11-19T08-44-36_188-jvmRun1.dumpstream
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  7.042 s
[INFO] Finished at: 2018-11-19T08:44:36+01:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test (default-test) on 
project myjob: There are test failures.
[ERROR]
[ERROR] Please refer to 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire-reports
 for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, 
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
[ERROR] Command was /bin/sh -c cd 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1 && 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
@/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire/surefireargs8795971990665471093
 
/home/bamboo/bamboo-prod-agent3-home/xml-data/build-dir/MYPLAN-MYJOB-JOB1/target/surefire
 2018-11-19T08-44-36_188-jvmRun1 surefire4807933959136996302tmp 
surefire_012123328341666595325tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:283)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1149)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:991)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:837)
[ERROR] at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at 

[jira] [Commented] (MJAVADOC-545) Struts 1.3.8

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691637#comment-16691637
 ] 

Michael Osipov commented on MJAVADOC-545:
-

That's a tricky one, it is a deep trans dep. The enitre Doxia change needs to 
switch to Velocity Engine 2.0 and Velocity Tools 3.0. If some newer version is 
binary compatible you can easily change his in your parent POM. Is that an 
option for you?

> Struts 1.3.8
> 
>
> Key: MJAVADOC-545
> URL: https://issues.apache.org/jira/browse/MJAVADOC-545
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>  Components: javadoc
>Affects Versions: 3.0.1
>Reporter: Chris Scott
>Priority: Major
>
> Our security audits have reported that this plugin has a dependency on Struts 
> 1.3.8 which has several critical security flaws. Although this is a 
> build-time only plugin, this still represents a security issue. That version 
> of Struts is also EOL which is far from ideal. Is there any way to update?
> [https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MENFORCER-306) [REGRESSION] RequirePluginVersions fails

[Joseph Walton (JIRA)]

[ 
https://issues.apache.org/jira/browse/MENFORCER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691557#comment-16691557
 ] 

Joseph Walton commented on MENFORCER-306:
-

I ran into this issue;  a more specific issue title might help others to find 
it ("requirePluginsVersions fails to recognise versions specified in parent 
poms from outside the reactor"?).

It looks like a [branch for this 
issue|https://github.com/apache/maven-enforcer/tree/MENFORCER-306] had a 
[potential 
fix|https://github.com/apache/maven-enforcer/commit/f503829ff3e0a05df9af8cf29d206693225a21b7]
 committed back in June. Was that a viable approach? Is it worth testing, 
suggesting feedback or proposing alternatives?

> [REGRESSION] RequirePluginVersions fails
> 
>
> Key: MENFORCER-306
> URL: https://issues.apache.org/jira/browse/MENFORCER-306
> Project: Maven Enforcer Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: MENFORCER-306.zip, pom.xml
>
>
> I have found that running the {{RequirePluginVersions}} rule on a project 
> with version {{3.0.0-M1}} works fine whereas it fails with version 
> {{3.0.0-M2}}.
> {code}
> [DEBUG] Executing rule: 
> org.apache.maven.plugins.enforcer.RequirePluginVersions
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG]   lifecycleMapping = clean
> [DEBUG]   plugins = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] plugin = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] GAV = [org.apache.maven.plugins, maven-clean-plugin, 2.5, clean]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG]   lifecycleMapping = install
> [DEBUG]   plugins = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] plugin = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] GAV = [org.apache.maven.plugins, maven-install-plugin, 2.4, 
> install]
> [DEBUG]   lifecycleMapping = deploy
> [DEBUG]   plugins = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-deploy-plugin, 2.7, deploy]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG]   lifecycleMapping = site
> [DEBUG]   plugins = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, site]
> [DEBUG]   lifecycleMapping = site-deploy
> [DEBUG]   plugins = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, deploy]
> [DEBUG] All Plugins in use: [Plugin [org.tinyjee.dim:doxia-include-macro], 
> Plugin [org.apache.maven.plugins:maven-clean-plugin], Plugin 
> [org.apache.maven.plugins:maven-install-plugin], Plugin 
> [org.apache.maven.plugins:maven-site-plugin], Plugin 
> [org.apache.maven.plugins:maven-deploy-plugin], Plugin 
> [org.jacoco:jacoco-maven-plugin], Plugin 
> [org.apache.maven.plugins:maven-enforcer-plugin]]
> [DEBUG] plugin org.tinyjee.dim:doxia-include-macro not found
> [DEBUG] plugin org.apache.maven.plugins:maven-clean-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-install-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-site-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-deploy-plugin not found
> [DEBUG] plugin org.jacoco:jacoco-maven-plugin not found
> [DEBUG] Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Some plugins are 
> missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed )
> org.tinyjee.dim:doxia-include-macro.  The version currently in use is 1.1
> org.apache.maven.plugins:maven-clean-plugin.  The version currently in use is 
> 3.0.0
> org.apache.maven.plugins:maven-install-plugin.The version currently 
> in use is 2.5.2
> org.apache.maven.plugins:maven-site-plugin.   The version currently in use is 
> 3.6
> org.apache.maven.plugins:maven-deploy-plugin. The version currently 
> in use is 2.8.2
> org.jacoco:jacoco-maven-plugin.   The version currently in use is 0.8.0
> Always define plugin versions! Never use LATEST or RELEASE.
> at org.apache.maven.plugins.enforcer.RequirePluginVersions.execute 
> (RequirePluginVersions.java:320)
> at org.apache.maven.plugins.enforcer.EnforceMojo.execute 
> (EnforceMojo.java:194)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {code}



--
This message was sent by Atlassian 

[jira] [Updated] (MJAVADOC-545) Struts 1.3.8

[Chris Scott (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Scott updated MJAVADOC-545:
-
Description: 
Our security audits have reported that this plugin has a dependency on Struts 
1.3.8 which has several critical security flaws. Although this is a build-time 
only plugin, this still represents a security issue as well as using EOL 
software. Is there any way to update?

[https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]

  was:
Our security audits have reported that this plugin has a dependency on Struts 
1.3.8 which has several critical security flaws. Although this is a 
build-time-only plugin, this still represents a security issue as well as using 
EOL software. Is there any way to update?

[https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]


> Struts 1.3.8
> 
>
> Key: MJAVADOC-545
> URL: https://issues.apache.org/jira/browse/MJAVADOC-545
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>  Components: javadoc
>Affects Versions: 3.0.1
>Reporter: Chris Scott
>Priority: Major
>
> Our security audits have reported that this plugin has a dependency on Struts 
> 1.3.8 which has several critical security flaws. Although this is a 
> build-time only plugin, this still represents a security issue as well as 
> using EOL software. Is there any way to update?
> [https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAVADOC-545) Struts 1.3.8

[Chris Scott (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Scott updated MJAVADOC-545:
-
Description: 
Our security audits have reported that this plugin has a dependency on Struts 
1.3.8 which has several critical security flaws. Although this is a build-time 
only plugin, this still represents a security issue. That version of Struts is 
also EOL which is far from ideal. Is there any way to update?

[https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]

  was:
Our security audits have reported that this plugin has a dependency on Struts 
1.3.8 which has several critical security flaws. Although this is a build-time 
only plugin, this still represents a security issue as well as using EOL 
software. Is there any way to update?

[https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]


> Struts 1.3.8
> 
>
> Key: MJAVADOC-545
> URL: https://issues.apache.org/jira/browse/MJAVADOC-545
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>  Components: javadoc
>Affects Versions: 3.0.1
>Reporter: Chris Scott
>Priority: Major
>
> Our security audits have reported that this plugin has a dependency on Struts 
> 1.3.8 which has several critical security flaws. Although this is a 
> build-time only plugin, this still represents a security issue. That version 
> of Struts is also EOL which is far from ideal. Is there any way to update?
> [https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MJAVADOC-545) Struts 1.3.8

[Chris Scott (JIRA)]

Chris Scott created MJAVADOC-545:


 Summary: Struts 1.3.8
 Key: MJAVADOC-545
 URL: https://issues.apache.org/jira/browse/MJAVADOC-545
 Project: Maven Javadoc Plugin
  Issue Type: Dependency upgrade
  Components: javadoc
Affects Versions: 3.0.1
Reporter: Chris Scott


Our security audits have reported that this plugin has a dependency on Struts 
1.3.8 which has several critical security flaws. Although this is a 
build-time-only plugin, this still represents a security issue as well as using 
EOL software. Is there any way to update?

[https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-6117/version_id-164423/Apache-Struts-1.3.8.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MINVOKER-245) Using an alternate toolchain file

[*$^¨%`£]

Olivier Lamy (*$^¨%`£) created MINVOKER-245:
---

 Summary: Using an alternate toolchain file
 Key: MINVOKER-245
 URL: https://issues.apache.org/jira/browse/MINVOKER-245
 Project: Maven Invoker Plugin
  Issue Type: Improvement
Reporter: Olivier Lamy (*$^¨%`£)
Assignee: Olivier Lamy (*$^¨%`£)
 Fix For: 3.1.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MCHECKSTYLE-344) StringIndexOutOfBoundsException in RuleUtil

[Daniel Wegener (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Wegener updated MCHECKSTYLE-344:
---
Comment: was deleted

(was: 
Hallo,

ich bin bis zum 17.11.2018 im Urlaub und bis dahin leider nicht erreichbar.

Beste Grüße

Daniel Wegener
Holisticon AG

Griegstraße 75, Haus 25
22763 Hamburg
Mobile: +49 176 1616 9025
Office: +49 40 6094 430-0
Fax:  +49 40 6094 430-30
E-Mail: daniel.wege...@holisticon.de
www.holisticon.de

Amtsgericht Hamburg, HRB 107396
Vorstand: Oliver Ihns, Dierk Harbeck
Aufsichtsrat: Sune Nilsson (Vorsitz)
)

> StringIndexOutOfBoundsException in RuleUtil
> ---
>
> Key: MCHECKSTYLE-344
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-344
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:check
>Affects Versions: 2.17
>Reporter: fdvxxii
>Assignee: Guillaume Boué
>Priority: Major
> Fix For: 3.0.1
>
>
> {{RuleUtil}} has a bug at line 95:
> {code}
>   final int end = eventSrcName.lastIndexOf('.');
>   eventSrcName = eventSrcName.substring(0, end);  
> {code}
> This code leads to a StringIndexOutOfBoundsException if the variable does not 
> contain a period. I don't know if its a convention to have a period in that 
> string, but either way the error message should me more expressive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSHARED-772) maven-dependency-analyzer not working on OpenJDK 11

[khalid el boukhari (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHARED-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691368#comment-16691368
 ] 

khalid el boukhari commented on MSHARED-772:


Thank for the replay. Yes maven-compiler-plugin works fine.

This issue is open here because the dep-analyzer doesn't work under jdk11. 

 

> maven-dependency-analyzer not working on OpenJDK 11 
> 
>
> Key: MSHARED-772
> URL: https://issues.apache.org/jira/browse/MSHARED-772
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Reporter: khalid el boukhari
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
>
> Hi,
> Maven-dependency-analyzer is not supporting java 11.
> Here is my conf : 
> {code:xml}
> 
> maven-compiler-plugin
> 
> 
> org.ow2.asm
> asm
> 7.0
> 
> 
> 
> 11
> 
> 
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)