[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756962#comment-16756962
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6071 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/8/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756953#comment-16756953
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #14
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/14/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756942#comment-16756942
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MAVEN-3.6/MNG-6399 #21
See
https://builds.apache.org/job/maven-box/job/maven/job/MAVEN-3.6%252FMNG-6399/21/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756940#comment-16756940
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #21
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/21/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756930#comment-16756930
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6294 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/8/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756926#comment-16756926
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #21
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/21/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756884#comment-16756884
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6405 #4
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6405/4/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756888#comment-16756888
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6543 #5
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6543/5/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756878#comment-16756878
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #8
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/8/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756876#comment-16756876
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #3
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/3/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756874#comment-16756874
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6553 #3
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/3/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756869#comment-16756869
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #3
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/3/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756865#comment-16756865
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #10
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/10/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756856#comment-16756856
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MPOM-215 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/2/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756866#comment-16756866
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #7
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/7/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756860#comment-16756860
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #6
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/6/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756855#comment-16756855
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6571 #7
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6571/7/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756853#comment-16756853
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » runITsWithJavaEA #16
See https://builds.apache.org/job/maven-box/job/maven/job/runITsWithJavaEA/16/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINSTALL-143) Move checksum generation from install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756734#comment-16756734 ] Christopher Tubbs commented on MINSTALL-143: [~beamerblvd], where do you see that recommendation "online"? Personally, I wouldn't recommend that. I just use maven-deploy-plugin and it works just fine when publishing to Sonatype Nexus repository manager staging repositories, and then use the UIs to close and/or release the repositories from there. I do not know what advantage nexus-staging-maven-plugin offers over maven-deploy-plugin, so perhaps there's some cool feature I'm missing out on... but I suspect not, since everything works just fine without it. > Move checksum generation from install to deploy plugin > -- > > Key: MINSTALL-143 > URL: https://issues.apache.org/jira/browse/MINSTALL-143 > Project: Maven Install Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-M1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0-M1 > > > We should move the checksum generation from maven-install-plugin to > maven-deploy-plugin cause the checksums will only be needed as a preparation > for the transfer to a remote repository but not for an installation into a > local repository. > This needed to be done within maven-artifact-transfer component first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINVOKER-247) NPE in InstallMojo
[
https://issues.apache.org/jira/browse/MINVOKER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) resolved MINVOKER-247.
-
Resolution: Fixed
avoid NPE with
[https://github.com/apache/maven-invoker-plugin/commit/e99a189e99cc655ed2f399cbb3d9f3a36625db4a]
But still not sure about the root cause.
> NPE in InstallMojo
> --
>
> Key: MINVOKER-247
> URL: https://issues.apache.org/jira/browse/MINVOKER-247
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Blocker
> Fix For: 3.2.1
>
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom
> (InstallMojo.java:387)
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectArtifacts
> (InstallMojo.java:325)
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectDependencies
> (InstallMojo.java:462)
> at org.apache.maven.plugins.invoker.InstallMojo.execute
> (InstallMojo.java:184){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MINVOKER-247) NPE in InstallMojo
[
https://issues.apache.org/jira/browse/MINVOKER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) updated MINVOKER-247:
Issue Type: Bug (was: Task)
> NPE in InstallMojo
> --
>
> Key: MINVOKER-247
> URL: https://issues.apache.org/jira/browse/MINVOKER-247
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Blocker
> Fix For: 3.2.1
>
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom
> (InstallMojo.java:387)
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectArtifacts
> (InstallMojo.java:325)
> at org.apache.maven.plugins.invoker.InstallMojo.installProjectDependencies
> (InstallMojo.java:462)
> at org.apache.maven.plugins.invoker.InstallMojo.execute
> (InstallMojo.java:184){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MINVOKER-247) NPE in InstallMojo
Olivier Lamy (*$^¨%`£) created MINVOKER-247:
---
Summary: NPE in InstallMojo
Key: MINVOKER-247
URL: https://issues.apache.org/jira/browse/MINVOKER-247
Project: Maven Invoker Plugin
Issue Type: Task
Affects Versions: 3.2.0
Reporter: Olivier Lamy (*$^¨%`£)
Assignee: Olivier Lamy (*$^¨%`£)
Fix For: 3.2.1
{code:java}
Caused by: java.lang.NullPointerException
at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom
(InstallMojo.java:387)
at org.apache.maven.plugins.invoker.InstallMojo.installProjectArtifacts
(InstallMojo.java:325)
at org.apache.maven.plugins.invoker.InstallMojo.installProjectDependencies
(InstallMojo.java:462)
at org.apache.maven.plugins.invoker.InstallMojo.execute
(InstallMojo.java:184){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHADE-311) Bad exclusions in dependency-reduced-pom.xml
Dmitri Gabbasov created MSHADE-311:
--
Summary: Bad exclusions in dependency-reduced-pom.xml
Key: MSHADE-311
URL: https://issues.apache.org/jira/browse/MSHADE-311
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 3.2.1
Environment: maven-shade-plugin 3.2.1
Maven 3.6.0
JDK 11
Reporter: Dmitri Gabbasov
Given the following dependency graph:
{noformat}
test:foo:jar:1.0.0-SNAPSHOT
+- test:foz:jar:1.0.0-SNAPSHOT:compile
\- test:bar:jar:1.0.0-SNAPSHOT:provided
\- test:baz:jar:1.0.0-SNAPSHOT:provided
{noformat}
where {{baz}} is a _compile_ scope dependency of {{bar}} (and therefore a
_provided_ scope dependency of {{foo}}). And given the following
maven-shade-plugin configuration in {{foo}}:
{noformat}
test:foz
{noformat}
A weird {{dependency-reduced-pom.xml}} file is produced for {{foo}}, where the
{{bar}} dependency declaration gets an exclusion for {{baz}}:
{noformat}
test
bar
1.0.0-SNAPSHOT
provided
baz
test
{noformat}
Such an exclusion is unexpected and seems wrong to me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] rturner-edjuster commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section
rturner-edjuster commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section URL: https://github.com/apache/maven-checkstyle-plugin/pull/9#issuecomment-459146750 Great stuff. 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
[GitHub] eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section
eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section URL: https://github.com/apache/maven-checkstyle-plugin/pull/9#issuecomment-459146598 No. CI tests passed the patch is good to go. I will merge tomorrow (don't have my laptop at the moment) Thank you very much 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] rturner-edjuster commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section
rturner-edjuster commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section URL: https://github.com/apache/maven-checkstyle-plugin/pull/9#issuecomment-459144316 Just wondering if there are steps you want me to take with the build (sorry, not committed to this project before). Let me know if you want me to do anything with it. 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] eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies
eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies URL: https://github.com/apache/maven-checkstyle-plugin/pull/5#issuecomment-459143477 See my previous comments above. This change will break other implementations not covered by testcases. IMO we should add test cases to demonstrate that we are not breaking such case (you can file separate PRs for each new integration test) Once we have such tests you will be able to eventually tune your patch in order not to break the issues spotted above 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] [Comment Edited] (MCOMPILER-369) Adding module-info.java breaks JMH annotation processor
[
https://issues.apache.org/jira/browse/MCOMPILER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756347#comment-16756347
]
Gili edited comment on MCOMPILER-369 at 1/30/19 10:45 PM:
--
I found an explanation:
[http://jigsaw-dev.1059479.n5.nabble.com/Annotation-processors-and-the-processor-module-path-tp5714320p5714342.html]
Alan Bateman writes:
{quote}When you deploy annotation processors on the --processor-module-path
then javac needs to resolve the annotation processor modules as part of
creating the dynamic configuration. The issue with the dependency on
java.xml.bind is that it's not in the boot layer and it's also not
observable on the processor module path. There is no support at this
time for augmenting the boot layer once it is created, also javac does
not attempt to resolve these modules from the original module path and
system image that were used to start the VM. So for now at least,
running with -J--add-modules=java.xml.bind is the only way to get this
to work.
{quote}
That said, I was unable to make it work under Java 11 because "java.xml.bind"
has been removed.
was (Author: cowwoc):
I found an explanation:
[http://jigsaw-dev.1059479.n5.nabble.com/Annotation-processors-and-the-processor-module-path-tp5714320p5714342.html]
Alan Bateman writes:
{quote}When you deploy annotation processors on the --processor-module-path
then javac needs to resolve the annotation processor modules as part of
creating the dynamic configuration. The issue with the dependency on
java.xml.bind is that it's not in the boot layer and it's also not
observable on the processor module path. There is no support at this
time for augmenting the boot layer once it is created, also javac does
not attempt to resolve these modules from the original module path and
system image that were used to start the VM. So for now at least,
running with -J--add-modules=java.xml.bind is the only way to get this
to work.
{quote}
> Adding module-info.java breaks JMH annotation processor
> ---
>
> Key: MCOMPILER-369
> URL: https://issues.apache.org/jira/browse/MCOMPILER-369
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
>Reporter: Gili
>Priority: Major
> Attachments: annotation-processor-jigsaw.zip
>
>
> # Open testcase
> # Run {{clean install}}. Notice that the benchmarks run.
> # Open {{pom.xml}} and comment-out the {{
> section.}}
> # Run {{clean install}}. Notice that the annotation processor does not run
> and the benchmarks break.
> # Delete/rename {{module-info.java}}.
> # Run {{clean install}}. Notice that the benchmarks work again.
> The documentation for {{}} states that by default
> annotation processors are detected from the classpath. It seems that adding
> {{module-info.java}} breaks that somehow, which is weird/unexpected because
> JMH exists as a dependency outside the newly-declared module.
> I did two things to prove that the annotation processor is not being invoked
> in step 4:
> # Notice that {{target/test-classes/META-INF}} is not created.
> # Place a breakpoint in {{org.openjdk.jmh.generators.BenchmarkProcessor}}
> and notice that it is never even constructed.
> I tried digging into the maven-compiler-plugin and plexus-compiler
> source-code but couldn't figure out where the problem is. The only workaround
> I found is to specify {{annotationProcessorPaths}} manually but it took me
> half a day to track down this problem.
> Any idea what is going on? Is this a bug in the plugin(s)?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MRESOLVER-7: Assignee: Sylwester Lachiewicz > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Assignee: Sylwester Lachiewicz >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-798) Add defaultEntries option
[
https://issues.apache.org/jira/browse/MSHARED-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756588#comment-16756588
]
Michael Osipov commented on MSHARED-798:
I haven't created it yet.
> Add defaultEntries option
> -
>
> Key: MSHARED-798
> URL: https://issues.apache.org/jira/browse/MSHARED-798
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Affects Versions: maven-archiver-3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-archiver-3.4.0
>
>
> Based on MSHARED-362 one should have the option to disable default
> (reproducible) manifest entries explicitly: {{Created-By}},
> {{Build-Jdk-Spec}} with the option {{addDefaultEntries: true}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1222) ForkClient attempts to consume unrelated lines
[
https://issues.apache.org/jira/browse/SUREFIRE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756580#comment-16756580
]
Tibor Digana commented on SUREFIRE-1222:
I will continue on this on Friday.
On Wed, Jan 30, 2019 at 9:49 PM Enrico Olivelli (JIRA)
> ForkClient attempts to consume unrelated lines
> --
>
> Key: SUREFIRE-1222
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1222
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.17
> Environment: Oracle JDK7 (build 1.7.0_79-b15)
> Linux 3.13 x86_64 with default locale cs_CZ
>Reporter: Martin Kouba
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This month the [Weld
> SE|https://github.com/weld/core/tree/2.3/environments/se/tests] test suite
> suddenly started to fail on a Linux machine with Oracle JDK7 and the default
> locale {{cs_CZ}}:
> {code}
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range: -1
> at java.lang.String.substring(String.java:1911)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:128)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> A {{java.util.logging.Logger}} is used in the forked process. The exception
> occurs when the following log message is written to the standard output:
> {code}
> I 29, 2016 2:01:43 ODP. org.jboss.arquillian.container.se.server.Main main
> {code}
> We have found out that the timestamp *I 29, 2016 2:01:43* (i.e. 2016-01-29
> 14:01:43) is incorrectly parsed as {{ForkingRunListener.BOOTERCODE_SYSPROPS}}
> operation.
> I think the protocol should be robust enough to avoid similar collisions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] gdubicki commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2
gdubicki commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-459119864 Hi @slachiewicz ! Were you able to get back to this? A lot of people would love to get this PR merged, see https://stackoverflow.com/questions/32299902/parallel-downloads-of-maven-artifacts/43832592 . :) 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] zregvart commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies
zregvart commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies URL: https://github.com/apache/maven-checkstyle-plugin/pull/5#issuecomment-459106071 @eolivelli yes, I can find the time. What would you say needs to be 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] [Commented] (SUREFIRE-1222) ForkClient attempts to consume unrelated lines
[
https://issues.apache.org/jira/browse/SUREFIRE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756545#comment-16756545
]
Enrico Olivelli commented on SUREFIRE-1222:
---
[~tibor17] so you will be back at this patch soon !
I will be happy to work then at the socket based implementation once we have
merged the Abstraction over the communication between forked jvm and master
process
> ForkClient attempts to consume unrelated lines
> --
>
> Key: SUREFIRE-1222
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1222
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.17
> Environment: Oracle JDK7 (build 1.7.0_79-b15)
> Linux 3.13 x86_64 with default locale cs_CZ
>Reporter: Martin Kouba
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This month the [Weld
> SE|https://github.com/weld/core/tree/2.3/environments/se/tests] test suite
> suddenly started to fail on a Linux machine with Oracle JDK7 and the default
> locale {{cs_CZ}}:
> {code}
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range: -1
> at java.lang.String.substring(String.java:1911)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:128)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> A {{java.util.logging.Logger}} is used in the forked process. The exception
> occurs when the following log message is written to the standard output:
> {code}
> I 29, 2016 2:01:43 ODP. org.jboss.arquillian.container.se.server.Main main
> {code}
> We have found out that the timestamp *I 29, 2016 2:01:43* (i.e. 2016-01-29
> 14:01:43) is incorrectly parsed as {{ForkingRunListener.BOOTERCODE_SYSPROPS}}
> operation.
> I think the protocol should be robust enough to avoid similar collisions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies
eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies URL: https://github.com/apache/maven-checkstyle-plugin/pull/5#issuecomment-459095625 @zregvart Do you have time to continue your work on this patch ? 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] eolivelli closed pull request #6: add initial .travis.yml
eolivelli closed pull request #6: add initial .travis.yml URL: https://github.com/apache/maven-checkstyle-plugin/pull/6 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] eolivelli commented on issue #6: add initial .travis.yml
eolivelli commented on issue #6: add initial .travis.yml URL: https://github.com/apache/maven-checkstyle-plugin/pull/6#issuecomment-459095370 @krichter722 I have committed now the standard Travis file for Maven plugins 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] eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section
eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section URL: https://github.com/apache/maven-checkstyle-plugin/pull/9#issuecomment-459094726 Here it is the CI job https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-365/ 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] eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section
eolivelli commented on issue #9: [MCHECKSTYLE-365] Correct counts in Rules section URL: https://github.com/apache/maven-checkstyle-plugin/pull/9#issuecomment-459086347 Sorry for so late reply. Will be back soon on this patch 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] (MSHARED-798) Add defaultEntries option
[
https://issues.apache.org/jira/browse/MSHARED-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756505#comment-16756505
]
Hervé Boutemy commented on MSHARED-798:
---
Notice: {{Created-By}} entry is not yet reproducible, since it still contains
Maven version instead of Maven Archiver version (with overrrides for plugins to
define the plugin using Maven Archiver)
I could not find the Jira issue where we discussed that...
> Add defaultEntries option
> -
>
> Key: MSHARED-798
> URL: https://issues.apache.org/jira/browse/MSHARED-798
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Affects Versions: maven-archiver-3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-archiver-3.4.0
>
>
> Based on MSHARED-362 one should have the option to disable default
> (reproducible) manifest entries explicitly: {{Created-By}},
> {{Build-Jdk-Spec}} with the option {{addDefaultEntries: true}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-798) Add defaultEntries option
[
https://issues.apache.org/jira/browse/MSHARED-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756490#comment-16756490
]
Hervé Boutemy commented on MSHARED-798:
---
I prefer {{addDefaultEntries}}, and explanation in the java doc of the
rationale for the choice of the entries
> Add defaultEntries option
> -
>
> Key: MSHARED-798
> URL: https://issues.apache.org/jira/browse/MSHARED-798
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Affects Versions: maven-archiver-3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-archiver-3.4.0
>
>
> Based on MSHARED-362 one should have the option to disable default
> (reproducible) manifest entries explicitly: {{Created-By}},
> {{Build-Jdk-Spec}} with the option {{addDefaultEntries: true}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-569) javadoc:aggregate fails with 'error: package org.w3c.dom is not visible' when mixing Java modules and non-modules
[
https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756453#comment-16756453
]
Robert Scholte commented on MJAVADOC-569:
-
I think this is by design. The module-summary shows the public or exported
packages. For module1 there are none. However the pages are generated so
module2 can refer to them.
> javadoc:aggregate fails with 'error: package org.w3c.dom is not visible' when
> mixing Java modules and non-modules
> -
>
> Key: MJAVADOC-569
> URL: https://issues.apache.org/jira/browse/MJAVADOC-569
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Environment: maven-javadoc-plugin 3.1.0-SNAPSHOT
> Java 12-ea+28
>Reporter: Gili
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: export-to-testcase.zip, testcase.zip
>
>
> # Unpack testcase
> # Run {{mvn clean package javadoc:aggregate -e}}
> # {{javadoc:aggregate}} will fail with various errors like "(package
> org.w3c.dom is declared in module java.xml, but module module2 does not read
> it)"
> Note that module 2 isn't really a Java Module but we are treating it as such
> for the purposes of aggregating Javadoc across modularized and
> non-modularized code. Module 2 has no way of declaring its intention of
> reading the aforementioned package because it does not have a
> {{module-info.java}} file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MCOMPILER-369) Adding module-info.java breaks JMH annotation processor
[
https://issues.apache.org/jira/browse/MCOMPILER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756347#comment-16756347
]
Gili commented on MCOMPILER-369:
I found an explanation:
[http://jigsaw-dev.1059479.n5.nabble.com/Annotation-processors-and-the-processor-module-path-tp5714320p5714342.html]
Alan Bateman writes:
{quote}When you deploy annotation processors on the --processor-module-path
then javac needs to resolve the annotation processor modules as part of
creating the dynamic configuration. The issue with the dependency on
java.xml.bind is that it's not in the boot layer and it's also not
observable on the processor module path. There is no support at this
time for augmenting the boot layer once it is created, also javac does
not attempt to resolve these modules from the original module path and
system image that were used to start the VM. So for now at least,
running with -J--add-modules=java.xml.bind is the only way to get this
to work.
{quote}
> Adding module-info.java breaks JMH annotation processor
> ---
>
> Key: MCOMPILER-369
> URL: https://issues.apache.org/jira/browse/MCOMPILER-369
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
>Reporter: Gili
>Priority: Major
> Attachments: annotation-processor-jigsaw.zip
>
>
> # Open testcase
> # Run {{clean install}}. Notice that the benchmarks run.
> # Open {{pom.xml}} and comment-out the {{
> section.}}
> # Run {{clean install}}. Notice that the annotation processor does not run
> and the benchmarks break.
> # Delete/rename {{module-info.java}}.
> # Run {{clean install}}. Notice that the benchmarks work again.
> The documentation for {{}} states that by default
> annotation processors are detected from the classpath. It seems that adding
> {{module-info.java}} breaks that somehow, which is weird/unexpected because
> JMH exists as a dependency outside the newly-declared module.
> I did two things to prove that the annotation processor is not being invoked
> in step 4:
> # Notice that {{target/test-classes/META-INF}} is not created.
> # Place a breakpoint in {{org.openjdk.jmh.generators.BenchmarkProcessor}}
> and notice that it is never even constructed.
> I tried digging into the maven-compiler-plugin and plexus-compiler
> source-code but couldn't figure out where the problem is. The only workaround
> I found is to specify {{annotationProcessorPaths}} manually but it took me
> half a day to track down this problem.
> Any idea what is going on? Is this a bug in the plugin(s)?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-569) javadoc:aggregate fails with 'error: package org.w3c.dom is not visible' when mixing Java modules and non-modules
[
https://issues.apache.org/jira/browse/MJAVADOC-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756060#comment-16756060
]
Gili commented on MJAVADOC-569:
---
[~rfscholte] Sorry to nudge, but do you plan to reopen this issue or should I
file a separate issue for all posts since this one was closed?
> javadoc:aggregate fails with 'error: package org.w3c.dom is not visible' when
> mixing Java modules and non-modules
> -
>
> Key: MJAVADOC-569
> URL: https://issues.apache.org/jira/browse/MJAVADOC-569
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Environment: maven-javadoc-plugin 3.1.0-SNAPSHOT
> Java 12-ea+28
>Reporter: Gili
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: export-to-testcase.zip, testcase.zip
>
>
> # Unpack testcase
> # Run {{mvn clean package javadoc:aggregate -e}}
> # {{javadoc:aggregate}} will fail with various errors like "(package
> org.w3c.dom is declared in module java.xml, but module module2 does not read
> it)"
> Note that module 2 isn't really a Java Module but we are treating it as such
> for the purposes of aggregating Javadoc across modularized and
> non-modularized code. Module 2 has no way of declaring its intention of
> reading the aforementioned package because it does not have a
> {{module-info.java}} file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6232) Version range is not resolved correctly
[ https://issues.apache.org/jira/browse/MNG-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755929#comment-16755929 ] Kemal Soysal commented on MNG-6232: --- I face this problem too. Maybe there could be stricter pattern like [1.7, 1.8[ to express any release version lesser than 1.8 without any -* > Version range is not resolved correctly > --- > > Key: MNG-6232 > URL: https://issues.apache.org/jira/browse/MNG-6232 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.3.3 >Reporter: Marek Budyn >Priority: Major > Attachments: pom.xml > > > When dependency is specified as range, e.g slf4j-api version [1.7, 1.8) as in > provided pom.xml, one would expect to resolver to version 1.7.X (e.g. > 1.7.25). Instead maven resolves version 1.8.0-alpha 2. > Output of command 'mvn dependenct:tree' on provided pom.xml: > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building project 1.0.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ project --- > [INFO] test:project:jar:1.0.0-SNAPSHOT > [INFO] \- org.slf4j:slf4j-api:jar:1.8.0-alpha2:compile > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 1.273 s > [INFO] Finished at: 2017-05-12T23:37:02+02:00 > [INFO] Final Memory: 13M/225M > [INFO] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
