[jira] [Commented] (MNG-6481) Allow to compile and test Maven with Java 11

2018-09-19 Thread Sylwester Lachiewicz (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621181#comment-16621181 ] Sylwester Lachiewicz commented on MNG-6481: --- I have build that pass compile and t

[jira] [Reopened] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened SUREFIRE-1570: -- Reopening. Using the same test with surefire does work as expected. When running with {{

[jira] [Comment Edited] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Pavel_K (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621031#comment-16621031 ] Pavel_K edited comment on SUREFIRE-1570 at 9/19/18 6:46 PM:

[jira] [Commented] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Pavel_K (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621031#comment-16621031 ] Pavel_K commented on SUREFIRE-1570: --- OK. Read JPMS specification. See also ServicePr

[jira] [Commented] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621013#comment-16621013 ] Robert Scholte commented on SUREFIRE-1570: -- bq. When we use JPMS we don't cre

[jira] [Commented] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Pavel_K (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620972#comment-16620972 ] Pavel_K commented on SUREFIRE-1570: --- No. This is not right. The way you described is

[jira] [Closed] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SUREFIRE-1570. Resolution: Not A Problem Assignee: Robert Scholte You've forgot to add the follow

[jira] [Commented] (MSHADE-300) Allow retention of module-info class by property

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MSHADE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620943#comment-16620943 ] Robert Scholte commented on MSHADE-300: --- I think this is an acceptable option. Prob

[jira] [Closed] (MCOMPILER-362) Change default source/target option to be a bit more modern

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MCOMPILER-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-362. Resolution: Won't Fix Assignee: Robert Scholte I'm going to close this as won't fi

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

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620931#comment-16620931 ] Robert Scholte commented on MJAVADOC-538: - Interesting, based on https://githu

[jira] [Commented] (MCOMPILER-278) Incremental build does not track inter-module dependencies.

2018-09-19 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620925#comment-16620925 ] Robert Scholte commented on MCOMPILER-278: -- So if I understand correctly this

[jira] [Created] (MENFORCER-318) Upgrading maven-enforcer-plugin from 1.4 to 1.4.1 or higher breaks maven-assembly-plugin

2018-09-19 Thread Marcel Schutte (JIRA)
Marcel Schutte created MENFORCER-318: Summary: Upgrading maven-enforcer-plugin from 1.4 to 1.4.1 or higher breaks maven-assembly-plugin Key: MENFORCER-318 URL: https://issues.apache.org/jira/browse/MENFORCER-3

[GitHub] mkarg opened a new pull request #5: Parameter `fileMapper` for unpack path rewriting

2018-09-19 Thread GitBox
mkarg opened a new pull request #5: Parameter `fileMapper` for unpack path rewriting URL: https://github.com/apache/maven-dependency-plugin/pull/5 The new parameter `fileMapper` (default: `null`) can be set to an implementation of the `org.codehaus.plexus.components.io.filemappers.FileMap

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

2018-09-19 Thread JIRA
Yoann Rodière created MJAVADOC-538: -- Summary: JVM "JAVA_TOOL_OPTIONS" or "_JAVA_OPTIONS" message detected as javadoc warning, triggers failure Key: MJAVADOC-538 URL: https://issues.apache.org/jira/browse/MJAVADO

[GitHub] s50600822 closed pull request #180: better performant for some Collection operations

2018-09-19 Thread GitBox
s50600822 closed pull request #180: better performant for some Collection operations URL: https://github.com/apache/maven/pull/180 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 fore

[jira] [Created] (MCOMPILER-362) Change default source/target option to be a bit more modern

2018-09-19 Thread theminecoder (JIRA)
theminecoder created MCOMPILER-362: -- Summary: Change default source/target option to be a bit more modern Key: MCOMPILER-362 URL: https://issues.apache.org/jira/browse/MCOMPILER-362 Project: Maven Co

[jira] [Commented] (MCOMPILER-278) Incremental build does not track inter-module dependencies.

2018-09-19 Thread Liwae Lamaa (JIRA)
[ https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620295#comment-16620295 ] Liwae Lamaa commented on MCOMPILER-278: --- Hi [~rfscholte], what do you think? >

[jira] [Updated] (MSHADE-300) Allow retention of module-info class by property

2018-09-19 Thread Rafael Winterhalter (JIRA)
[ https://issues.apache.org/jira/browse/MSHADE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Winterhalter updated MSHADE-300: --- Attachment: MSHADE300.patch > Allow retention of module-info class by property >

[jira] [Created] (MSHADE-300) Allow retention of module-info class by property

2018-09-19 Thread Rafael Winterhalter (JIRA)
Rafael Winterhalter created MSHADE-300: -- Summary: Allow retention of module-info class by property Key: MSHADE-300 URL: https://issues.apache.org/jira/browse/MSHADE-300 Project: Maven Shade Plugin