[jira] [Closed] (WAGON-489) Java 7 required

2017-07-04 Thread *$^¨%`£ 

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

Olivier Lamy (*$^¨%`£) closed WAGON-489.

Resolution: Fixed

> Java 7 required
> ---
>
> Key: WAGON-489
> URL: https://issues.apache.org/jira/browse/WAGON-489
> Project: Maven Wagon
>  Issue Type: Bug
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.13
>
>
> for the record and make [~michael-o] happy :P



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (WAGON-489) Java 7 required

2017-07-04 Thread *$^¨%`£ 
Olivier Lamy (*$^¨%`£) created WAGON-489:


 Summary: Java 7 required
 Key: WAGON-489
 URL: https://issues.apache.org/jira/browse/WAGON-489
 Project: Maven Wagon
  Issue Type: Bug
Reporter: Olivier Lamy (*$^¨%`£)
Assignee: Olivier Lamy (*$^¨%`£)
 Fix For: 2.13


for the record and make [~michael-o] happy :P



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
I don't follow. When I run an install from any level, the 
`org.apache.maven.surefire:it-parent:1.0:pom` artifact 
(surefire-integration-tests/src/test/resources/pom.xml) does not get installed 
in to the IT repo (surefire-setup-integration-tests/target/it-repo). Am I 
missing something?

In order to execute an IT across multiple lifecycles, that POM needs to be 
installed it in to the local repository specified by failsafe.

It looks to me like every IT that references `it-parent` does so via a 
relative path (explicitly or by default). They never have to rely on the 
artifact resolver.


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
No, no.
No worries.
You should build entire project `mvn install` and not the individual IT.
The ITs cannot run separately, you can trigger it from building entire 
project from root in git.


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
One workaround for this would be to install the missing `it-parent` POM as 
part of my first lifecycle (i.e. mid-test). But this seems kind of hacky.

```

surefire-569-testjar
...



org.apache.maven.plugins
maven-install-plugin



install-file

install

${project.basedir}/../pom.xml
${project.basedir}/../pom.xml







```


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
Looking at it a bit deeper, looks like the root cause is that the 
`it-parent` POM is not installed in the IT repo. The issue isn't the dependency 
itself.


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
I've put together an integration test that can validate the execution of 
[SUREFIRE-1383](https://issues.apache.org/jira/browse/SUREFIRE-1383). And all 
is good on that front.

While I was poking around the other ITs, I tripped on the IT for 
[SUREFIRE-569](https://issues.apache.org/jira/browse/SUREFIRE-569). As written, 
the IT passes just fine. But the changes that I'm proposing make that test case 
moot - it uses the same packaging structure of 2 projects built within a single 
session.

I updated that test case to better reflect the original ask of scanning 
**_JAR_** dependencies, but that means splitting the test case execution in to 
2 separate lifecycles. When I split the single lifecycle in to 2, I'm running 
in to a dependency resolution issue. For whatever reason, the second execution 
is unable to locate artifacts installed in the IT repo as part of the first 
lifecycle.

In looking around at the other ITs, it looks like this is the only test 
case that runs an install goal and **_is then dependent on the result of that 
install_**.

Thoughts?
```
mvn 
-Dit.test=**/Surefire569RunTestFromDependencyJarsIT.java,**/Surefire1383ScanSessionDependenciesIT.java
 clean integration-test`
...
[DEBUG] Using local repository at 
//maven-surefire/surefire-integration-tests/../surefire-setup-integration-tests/target/it-repo
...
[ERROR] Failed to execute goal on project surefire-569-module1: Could not 
resolve dependencies for project 
org.apache.maven.surefire:surefire-569-module1:jar:1.0: Failed to collect 
dependencies at org.apache.maven.surefire:surefire-569-testjar:jar:tests:1.0: 
Failed to read artifact descriptor for 
org.apache.maven.surefire:surefire-569-testjar:jar:tests:1.0: Failure to find 
org.apache.maven.surefire:it-parent:pom:1.0 in 
https://repo.maven.apache.org/maven2 was cached in the local repository, 
resolution will not be reattempted until the update interval of central has 
elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
goal on project surefire-569-module1: Could not resolve dependencies for 
project org.apache.maven.surefire:surefire-569-module1:jar:1.0: Failed to 
collect dependencies at 
org.apache.maven.surefire:surefire-569-testjar:jar:tests:1.0
```


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MCHECKSTYLE-339) Incompatible with Checkstyle 8.0

2017-07-04 Thread Brent Plump (JIRA) 

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

Brent Plump closed MCHECKSTYLE-339.
---
Resolution: Invalid

> Incompatible with Checkstyle 8.0
> 
>
> Key: MCHECKSTYLE-339
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-339
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:check
>Affects Versions: 2.17
> Environment: maven 3.3.9
> macOS 10.12.5
>Reporter: Brent Plump
>
> maven-checkstyle-plugin 2.17 is incompatible with [Checkstyle 
> 8.0|http://checkstyle.sourceforge.net/releasenotes.html#Release_8.0] because 
> [Checkstyle 8.0 removed the {{Check}} 
> class|https://github.com/checkstyle/checkstyle/issues/4541] which is used by 
> the plugin.
> Full error log:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project bitbucket-parent: Execution default-cli of goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: A 
> required class was missing while executing 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check: 
> com/puppycrawl/tools/checkstyle/api/Check
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.17
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.jar
> [ERROR] urls[1] = 
> file:/Users/bplump/.m2/repository/com/puppycrawl/tools/checkstyle/8.0/checkstyle-8.0.jar
> [ERROR] urls[2] = 
> file:/Users/bplump/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar
> [ERROR] urls[3] = 
> file:/Users/bplump/.m2/repository/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar
> [ERROR] urls[4] = 
> file:/Users/bplump/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar
> [ERROR] urls[5] = 
> file:/Users/bplump/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
> [ERROR] urls[6] = 
> file:/Users/bplump/.m2/repository/com/google/guava/guava/22.0/guava-22.0.jar
> [ERROR] urls[7] = 
> file:/Users/bplump/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
> [ERROR] urls[8] = 
> file:/Users/bplump/.m2/repository/com/google/errorprone/error_prone_annotations/2.0.18/error_prone_annotations-2.0.18.jar
> [ERROR] urls[9] = 
> file:/Users/bplump/.m2/repository/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
> [ERROR] urls[10] = 
> file:/Users/bplump/.m2/repository/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
> [ERROR] urls[11] = 
> file:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/../lib/tools.jar
> [ERROR] urls[12] = 
> file:/Users/bplump/.m2/repository/com/atlassian/stash/stash-checkstyle/0.9.5/stash-checkstyle-0.9.5.jar
> [ERROR] urls[13] = 
> file:/Users/bplump/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
> [ERROR] urls[14] = 
> file:/Users/bplump/.m2/repository/com/atlassian/checkstyle-custom-checks/0.9.3/checkstyle-custom-checks-0.9.3.jar
> [ERROR] urls[15] = 
> file:/Users/bplump/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
> [ERROR] urls[16] = 
> file:/Users/bplump/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
> [ERROR] urls[17] = 
> file:/Users/bplump/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[18] = 
> file:/Users/bplump/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
> [ERROR] urls[19] = 
> file:/Users/bplump/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[20] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[21] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[22] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[23] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
> [ERROR] urls[24] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> [ERROR] urls[25] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
> [ERROR] urls[26] = 
> file:/Users/bplump/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
> [ERROR] urls[27] = 
>

[jira] [Commented] (MCHECKSTYLE-339) Incompatible with Checkstyle 8.0

2017-07-04 Thread Brent Plump (JIRA) 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074119#comment-16074119
 ] 

Brent Plump commented on MCHECKSTYLE-339:
-

[~gboue] - You're completely right, the problem is with our custom rules. Very 
sorry to waste your time with this.

> Incompatible with Checkstyle 8.0
> 
>
> Key: MCHECKSTYLE-339
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-339
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:check
>Affects Versions: 2.17
> Environment: maven 3.3.9
> macOS 10.12.5
>Reporter: Brent Plump
>
> maven-checkstyle-plugin 2.17 is incompatible with [Checkstyle 
> 8.0|http://checkstyle.sourceforge.net/releasenotes.html#Release_8.0] because 
> [Checkstyle 8.0 removed the {{Check}} 
> class|https://github.com/checkstyle/checkstyle/issues/4541] which is used by 
> the plugin.
> Full error log:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project bitbucket-parent: Execution default-cli of goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: A 
> required class was missing while executing 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check: 
> com/puppycrawl/tools/checkstyle/api/Check
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.17
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.jar
> [ERROR] urls[1] = 
> file:/Users/bplump/.m2/repository/com/puppycrawl/tools/checkstyle/8.0/checkstyle-8.0.jar
> [ERROR] urls[2] = 
> file:/Users/bplump/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar
> [ERROR] urls[3] = 
> file:/Users/bplump/.m2/repository/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar
> [ERROR] urls[4] = 
> file:/Users/bplump/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar
> [ERROR] urls[5] = 
> file:/Users/bplump/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
> [ERROR] urls[6] = 
> file:/Users/bplump/.m2/repository/com/google/guava/guava/22.0/guava-22.0.jar
> [ERROR] urls[7] = 
> file:/Users/bplump/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
> [ERROR] urls[8] = 
> file:/Users/bplump/.m2/repository/com/google/errorprone/error_prone_annotations/2.0.18/error_prone_annotations-2.0.18.jar
> [ERROR] urls[9] = 
> file:/Users/bplump/.m2/repository/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
> [ERROR] urls[10] = 
> file:/Users/bplump/.m2/repository/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
> [ERROR] urls[11] = 
> file:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/../lib/tools.jar
> [ERROR] urls[12] = 
> file:/Users/bplump/.m2/repository/com/atlassian/stash/stash-checkstyle/0.9.5/stash-checkstyle-0.9.5.jar
> [ERROR] urls[13] = 
> file:/Users/bplump/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
> [ERROR] urls[14] = 
> file:/Users/bplump/.m2/repository/com/atlassian/checkstyle-custom-checks/0.9.3/checkstyle-custom-checks-0.9.3.jar
> [ERROR] urls[15] = 
> file:/Users/bplump/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
> [ERROR] urls[16] = 
> file:/Users/bplump/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
> [ERROR] urls[17] = 
> file:/Users/bplump/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[18] = 
> file:/Users/bplump/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
> [ERROR] urls[19] = 
> file:/Users/bplump/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[20] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[21] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[22] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[23] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
> [ERROR] urls[24] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> [ERROR] urls[25] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
> [ERROR] urls[26] = 
>

[jira] [Commented] (MPH-122) add help:color-style goal to describe styles color

2017-07-04 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/MPH-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074087#comment-16074087
 ] 

Guillaume Boué commented on MPH-122:


There needs to be a method in Maven Shared Utils to display all possible 
colors. What about having {{List getAvailableColorNames()}} in 
{{MessageUtils}} so that the plugin does not depend on Jansi?

{{org.apache.maven.shared.utils.logging.Style}} contains the current color 
style but it is package-private because Jansi specific. I think the Jansi 
specific parts can be refactored into {{AnsiMessageBuilder}} so that the 
{{Style}} enum can be made public and available to the Help Plugin.

> add help:color-style goal to describe styles color
> --
>
> Key: MPH-122
> URL: https://issues.apache.org/jira/browse/MPH-122
> Project: Maven Help Plugin
>  Issue Type: New Feature
>Affects Versions: 2.2
>Reporter: Hervé Boutemy
>
> as discussed on users@maven ML: 
> https://lists.apache.org/thread.html/09fa512d289a02c3c7d5262cbeff3285fe36e7eaa935528de69191ac@%3Cusers.maven.apache.org%3E
> bq. I vote for a help plugin goal, like help:color-style. It could show a 
> brief summary and how to customize, list available settings, and print active 
> settings.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

2017-07-04 Thread M.P. Korstanje (JIRA) 

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

M.P. Korstanje commented on SUREFIRE-1372:
--

This issue can not be resolved until cucumber 2.0.0 is done. We're wrapping up. 

However at the moment it is two people and their spare time so it could be 
anywhere between a month or six. 

Please do not wait for cucumber.

> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIASITETOOLS-178) Upgrade to Commons Lang 3

2017-07-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DOXIASITETOOLS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074076#comment-16074076
 ] 

ASF GitHub Bot commented on DOXIASITETOOLS-178:
---

Github user asfgit closed the pull request at:

https://github.com/apache/maven-doxia-sitetools/pull/4


> Upgrade to Commons Lang 3
> -
>
> Key: DOXIASITETOOLS-178
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-178
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.7.4
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.7.5
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPH-123) all-profiles does not show right active status

2017-07-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/MPH-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074074#comment-16074074
 ] 

Hudson commented on MPH-123:


SUCCESS: Integrated in Jenkins build maven-plugins #9020 (See 
[https://builds.apache.org/job/maven-plugins/9020/])
[MPH-123] all-profiles does not show right active status

MavenProject.getActiveProfiles only considers profiles from the project POM, so 
we also need to get the active profiles from the parents. With Maven 3, while 
it would be possible to use MavenProject.getInjectedProfileIds, it is more 
direct and symmetrical here to walk the parent chain ourselves (and makes sure 
the printed 'source' is consistent for active and inactive profiles from the 
settings). (gboue: [http://svn.apache.org/viewvc/?view=rev=1800814])
* (add) maven-help-plugin/src/it/all-profiles-parent-pom
* (add) maven-help-plugin/src/it/all-profiles-parent-pom/child
* (add) maven-help-plugin/src/it/all-profiles-parent-pom/child/pom.xml
* (add) maven-help-plugin/src/it/all-profiles-parent-pom/invoker.properties
* (add) maven-help-plugin/src/it/all-profiles-parent-pom/pom.xml
* (add) maven-help-plugin/src/it/all-profiles-parent-pom/verify.groovy
* (edit) 
maven-help-plugin/src/main/java/org/apache/maven/plugins/help/AllProfilesMojo.java
* (edit) 
maven-help-plugin/src/test/java/org/apache/maven/plugins/help/AllProfilesMojoTest.java


> all-profiles does not show right active status
> --
>
> Key: MPH-123
> URL: https://issues.apache.org/jira/browse/MPH-123
> Project: Maven Help Plugin
>  Issue Type: Bug
>  Components: all-profiles
>Affects Versions: 2.2
>Reporter: Mahendran Mookkiah
>Assignee: Guillaume Boué
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: hello-parent.zip, output.txt
>
>
> In multi-module project, help:all-profiles shows profiles of child project 
> are not active. But it is active and the profile plugins get executed.
> whereas active-profiles shows the right status. 
> Attached an example project which executed with below command and snippet of 
> result.
> Command: mvn help:all-profiles help:active-profiles -Pbuild-site
> Output snippet: 
> [INFO] Listing Profiles for Project: 
> com.example:hello-parent:pom:0.0.1-SNAPSHOT
>   Profile Id: build-site (Active: true , Source: pom)
>   Profile Id: artifactory (Active: true , Source: settings.xml)
> Listing Profiles for Project: com.example:helloworld:jar:0.0.1-SNAPSHOT
>   Profile Id: artifactory (Active: true , Source: settings.xml)
>   Profile Id: build-site (Active: false , Source: pom)  
> <<<=== shows not active 
> [INFO]
> [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ hello-parent 
> --
> -
> [INFO]
> Active Profiles for Project 'com.example:hello-parent:pom:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)
> Active Profiles for Project 'com.example:helloworld:jar:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)  
> <<<=== shows active



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MCHECKSTYLE-339) Incompatible with Checkstyle 8.0

2017-07-04 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074069#comment-16074069
 ] 

Guillaume Boué commented on MCHECKSTYLE-339:


Can you share a sample project? I cannot reproduce this running {{mvn 
checkstyle:check}} or {{mvn checkstyle:checkstyle}} with a project having

{code:xml}

  maven-checkstyle-plugin
  2.17
  

  com.puppycrawl.tools
  checkstyle
  8.0

  

{code}
I don't see where the plugin could be using the {{Check}} class directly.

> Incompatible with Checkstyle 8.0
> 
>
> Key: MCHECKSTYLE-339
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-339
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:check
>Affects Versions: 2.17
> Environment: maven 3.3.9
> macOS 10.12.5
>Reporter: Brent Plump
>
> maven-checkstyle-plugin 2.17 is incompatible with [Checkstyle 
> 8.0|http://checkstyle.sourceforge.net/releasenotes.html#Release_8.0] because 
> [Checkstyle 8.0 removed the {{Check}} 
> class|https://github.com/checkstyle/checkstyle/issues/4541] which is used by 
> the plugin.
> Full error log:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
> project bitbucket-parent: Execution default-cli of goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: A 
> required class was missing while executing 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check: 
> com/puppycrawl/tools/checkstyle/api/Check
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.17
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.jar
> [ERROR] urls[1] = 
> file:/Users/bplump/.m2/repository/com/puppycrawl/tools/checkstyle/8.0/checkstyle-8.0.jar
> [ERROR] urls[2] = 
> file:/Users/bplump/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar
> [ERROR] urls[3] = 
> file:/Users/bplump/.m2/repository/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar
> [ERROR] urls[4] = 
> file:/Users/bplump/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar
> [ERROR] urls[5] = 
> file:/Users/bplump/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
> [ERROR] urls[6] = 
> file:/Users/bplump/.m2/repository/com/google/guava/guava/22.0/guava-22.0.jar
> [ERROR] urls[7] = 
> file:/Users/bplump/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
> [ERROR] urls[8] = 
> file:/Users/bplump/.m2/repository/com/google/errorprone/error_prone_annotations/2.0.18/error_prone_annotations-2.0.18.jar
> [ERROR] urls[9] = 
> file:/Users/bplump/.m2/repository/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
> [ERROR] urls[10] = 
> file:/Users/bplump/.m2/repository/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
> [ERROR] urls[11] = 
> file:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/../lib/tools.jar
> [ERROR] urls[12] = 
> file:/Users/bplump/.m2/repository/com/atlassian/stash/stash-checkstyle/0.9.5/stash-checkstyle-0.9.5.jar
> [ERROR] urls[13] = 
> file:/Users/bplump/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
> [ERROR] urls[14] = 
> file:/Users/bplump/.m2/repository/com/atlassian/checkstyle-custom-checks/0.9.3/checkstyle-custom-checks-0.9.3.jar
> [ERROR] urls[15] = 
> file:/Users/bplump/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
> [ERROR] urls[16] = 
> file:/Users/bplump/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
> [ERROR] urls[17] = 
> file:/Users/bplump/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[18] = 
> file:/Users/bplump/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
> [ERROR] urls[19] = 
> file:/Users/bplump/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[20] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[21] = 
> file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[22] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[23] = 
> file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
> [ERROR] urls[24] = 
>

[jira] [Updated] (MPH-123) all-profiles does not show right active status

2017-07-04 Thread JIRA 

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

Guillaume Boué updated MPH-123:
---
Labels:   (was: maven)

> all-profiles does not show right active status
> --
>
> Key: MPH-123
> URL: https://issues.apache.org/jira/browse/MPH-123
> Project: Maven Help Plugin
>  Issue Type: Bug
>  Components: all-profiles
>Affects Versions: 2.2
>Reporter: Mahendran Mookkiah
>Assignee: Guillaume Boué
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: hello-parent.zip, output.txt
>
>
> In multi-module project, help:all-profiles shows profiles of child project 
> are not active. But it is active and the profile plugins get executed.
> whereas active-profiles shows the right status. 
> Attached an example project which executed with below command and snippet of 
> result.
> Command: mvn help:all-profiles help:active-profiles -Pbuild-site
> Output snippet: 
> [INFO] Listing Profiles for Project: 
> com.example:hello-parent:pom:0.0.1-SNAPSHOT
>   Profile Id: build-site (Active: true , Source: pom)
>   Profile Id: artifactory (Active: true , Source: settings.xml)
> Listing Profiles for Project: com.example:helloworld:jar:0.0.1-SNAPSHOT
>   Profile Id: artifactory (Active: true , Source: settings.xml)
>   Profile Id: build-site (Active: false , Source: pom)  
> <<<=== shows not active 
> [INFO]
> [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ hello-parent 
> --
> -
> [INFO]
> Active Profiles for Project 'com.example:hello-parent:pom:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)
> Active Profiles for Project 'com.example:helloworld:jar:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)  
> <<<=== shows active



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MPH-123) all-profiles does not show right active status

2017-07-04 Thread JIRA 

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

Guillaume Boué closed MPH-123.
--
   Resolution: Fixed
 Assignee: Guillaume Boué
Fix Version/s: 3.0.0

> all-profiles does not show right active status
> --
>
> Key: MPH-123
> URL: https://issues.apache.org/jira/browse/MPH-123
> Project: Maven Help Plugin
>  Issue Type: Bug
>  Components: all-profiles
>Affects Versions: 2.2
>Reporter: Mahendran Mookkiah
>Assignee: Guillaume Boué
>Priority: Minor
>  Labels: maven
> Fix For: 3.0.0
>
> Attachments: hello-parent.zip, output.txt
>
>
> In multi-module project, help:all-profiles shows profiles of child project 
> are not active. But it is active and the profile plugins get executed.
> whereas active-profiles shows the right status. 
> Attached an example project which executed with below command and snippet of 
> result.
> Command: mvn help:all-profiles help:active-profiles -Pbuild-site
> Output snippet: 
> [INFO] Listing Profiles for Project: 
> com.example:hello-parent:pom:0.0.1-SNAPSHOT
>   Profile Id: build-site (Active: true , Source: pom)
>   Profile Id: artifactory (Active: true , Source: settings.xml)
> Listing Profiles for Project: com.example:helloworld:jar:0.0.1-SNAPSHOT
>   Profile Id: artifactory (Active: true , Source: settings.xml)
>   Profile Id: build-site (Active: false , Source: pom)  
> <<<=== shows not active 
> [INFO]
> [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ hello-parent 
> --
> -
> [INFO]
> Active Profiles for Project 'com.example:hello-parent:pom:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)
> Active Profiles for Project 'com.example:helloworld:jar:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)  
> <<<=== shows active



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPH-123) all-profiles does not show right active status

2017-07-04 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/MPH-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074060#comment-16074060
 ] 

Guillaume Boué commented on MPH-123:


Fixed in [r1800814|http://svn.apache.org/viewvc?rev=1800814=rev].

> all-profiles does not show right active status
> --
>
> Key: MPH-123
> URL: https://issues.apache.org/jira/browse/MPH-123
> Project: Maven Help Plugin
>  Issue Type: Bug
>  Components: all-profiles
>Affects Versions: 2.2
>Reporter: Mahendran Mookkiah
>Priority: Minor
>  Labels: maven
> Attachments: hello-parent.zip, output.txt
>
>
> In multi-module project, help:all-profiles shows profiles of child project 
> are not active. But it is active and the profile plugins get executed.
> whereas active-profiles shows the right status. 
> Attached an example project which executed with below command and snippet of 
> result.
> Command: mvn help:all-profiles help:active-profiles -Pbuild-site
> Output snippet: 
> [INFO] Listing Profiles for Project: 
> com.example:hello-parent:pom:0.0.1-SNAPSHOT
>   Profile Id: build-site (Active: true , Source: pom)
>   Profile Id: artifactory (Active: true , Source: settings.xml)
> Listing Profiles for Project: com.example:helloworld:jar:0.0.1-SNAPSHOT
>   Profile Id: artifactory (Active: true , Source: settings.xml)
>   Profile Id: build-site (Active: false , Source: pom)  
> <<<=== shows not active 
> [INFO]
> [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ hello-parent 
> --
> -
> [INFO]
> Active Profiles for Project 'com.example:hello-parent:pom:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)
> Active Profiles for Project 'com.example:helloworld:jar:0.0.1-SNAPSHOT':
> The following profiles are active:
>  - artifactory (source: external)
>  - build-site (source: com.example:hello-parent:0.0.1-SNAPSHOT)  
> <<<=== shows active



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps

2017-07-04 Thread Robert Scholte (JIRA) 

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

Robert Scholte commented on MENFORCER-276:
--

This one is tricky. The original definition is that every GA can have only 1 
version, no matter the scope. This means you can change the version of a 
transitive compile-scoped dependency with a direct test-scoped dependency. We 
need to analyze the impact if we can improve this in a new major version of 
Maven.
So I'm not sure if this request does reflect the preferred behavior.

> Allow ignoring dependency scopes in RequireUpperBoundDeps
> -
>
> Key: MENFORCER-276
> URL: https://issues.apache.org/jira/browse/MENFORCER-276
> Project: Maven Enforcer Plugin
>  Issue Type: New Feature
>Reporter: Oleg Nenashev
>
> We have recently adopted RequireUpperBoundDeps in the Jenkins project 
> (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, 
> [~jgl...@netbeans.org] added a support of ignoring particular dependencies in 
> MENFORCER-273.
> Sometimes we declare dependencies between plugins for testing purposes 
> (scope=test), and in such case RequireUpperBoundDeps fails the build if there 
> is a test dependency conflicting with the main code. Although it may cause 
> instability of tests (including false positive results), it does not really 
> impact the distributable package in our case.
> I propose to add another option for filtering of dependency scopes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIASITETOOLS-178) Upgrade to Commons Lang 3

2017-07-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/DOXIASITETOOLS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074051#comment-16074051
 ] 

Hudson commented on DOXIASITETOOLS-178:
---

SUCCESS: Integrated in Jenkins build doxia-all #333 (See 
[https://builds.apache.org/job/doxia-all/333/])
[DOXIASITETOOLS-178] Upgrade to Commons Lang 3

Philippe Marschall 

This closes #4 (michaelo: [http://svn.apache.org/viewvc/?view=rev=1800812])
* (edit) ./doxia-sitetools/doxia-site-renderer/pom.xml
* (edit) 
./doxia-sitetools/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java


> Upgrade to Commons Lang 3
> -
>
> Key: DOXIASITETOOLS-178
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-178
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.7.4
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.7.5
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (DOXIASITETOOLS-177) Use of commons-lang 2 causes failure with JDK 9 b175+

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov closed DOXIASITETOOLS-177.
-
Resolution: Fixed

Fixed with [r1800812|http://svn.apache.org/r1800812].

> Use of commons-lang 2 causes failure with JDK 9 b175+
> -
>
> Key: DOXIASITETOOLS-177
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-177
> Project: Maven Doxia Sitetools
>  Issue Type: Bug
>  Components: Site renderer
>Affects Versions: 1.7.4
>Reporter: Anthony Vanelverdinghe
>Assignee: Michael Osipov
> Fix For: 1.7.5
>
>
> When doing a release of a Maven project, I get the stacktrace below. Since 
> JDK 9 b175, the java.version system property is simply "9". However, Doxia 
> depends on commons-lang 2.4, which assumes java.version has at least 3 
> characters.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:181)
>   ... 21 more
> Caused by: java.lang.ExceptionInInitializerError
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.generateDocument(DefaultSiteRenderer.java:732)
>   at 
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:268)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
>   at 
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:178)
>   at 
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   ... 21 more
> Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1
>   at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3116)
>   at java.base/java.lang.String.substring(String.java:1885)
>   at 
> org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1133)
>   at org.apache.commons.lang.SystemUtils.(SystemUtils.java:818)
>   ... 27 more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (DOXIASITETOOLS-178) Upgrade to Commons Lang 3

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov closed DOXIASITETOOLS-178.
-
Resolution: Fixed

Fixed with [r1800812|http://svn.apache.org/r1800812].

> Upgrade to Commons Lang 3
> -
>
> Key: DOXIASITETOOLS-178
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-178
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.7.4
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.7.5
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIA-558) Upgrade to Commons Lang 3

2017-07-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DOXIA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074037#comment-16074037
 ] 

ASF GitHub Bot commented on DOXIA-558:
--

Github user asfgit closed the pull request at:

https://github.com/apache/maven-doxia/pull/3


> Upgrade to Commons Lang 3
> -
>
> Key: DOXIA-558
> URL: https://issues.apache.org/jira/browse/DOXIA-558
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.7
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.8
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (DOXIASITETOOLS-178) Upgrade to Commons Lang 3

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov updated DOXIASITETOOLS-178:
--
Summary: Upgrade to Commons Lang 3  (was: Upgrade to commons-lang3)

> Upgrade to Commons Lang 3
> -
>
> Key: DOXIASITETOOLS-178
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-178
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.7.4
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.7.5
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIA-558) Upgrade to Commons Lang 3

2017-07-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/DOXIA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074035#comment-16074035
 ] 

Hudson commented on DOXIA-558:
--

SUCCESS: Integrated in Jenkins build doxia-all #332 (See 
[https://builds.apache.org/job/doxia-all/332/])
[DOXIA-558] Upgrade to Commons Lang 3

Philippe Marschall 

This closes #3 (michaelo: [http://svn.apache.org/viewvc/?view=rev=1800811])
* (edit) ./doxia/doxia-core/pom.xml
* (edit) 
./doxia/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java
* (edit) 
./doxia/doxia-core/src/test/java/org/apache/maven/doxia/sink/impl/SinkEventElement.java
* (edit) 
./doxia/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java


> Upgrade to Commons Lang 3
> -
>
> Key: DOXIA-558
> URL: https://issues.apache.org/jira/browse/DOXIA-558
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.7
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.8
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (DOXIA-558) Upgrade to Commons Lang 3

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov closed DOXIA-558.

Resolution: Fixed

Fixed with [r1800811|http://svn.apache.org/r1800811].

> Upgrade to Commons Lang 3
> -
>
> Key: DOXIA-558
> URL: https://issues.apache.org/jira/browse/DOXIA-558
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.7
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.8
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (DOXIA-558) Upgrade to Commons Lang 3

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov updated DOXIA-558:
-
Summary: Upgrade to Commons Lang 3  (was: Upgrade to commons-lang3)

> Upgrade to Commons Lang 3
> -
>
> Key: DOXIA-558
> URL: https://issues.apache.org/jira/browse/DOXIA-558
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.7
>Reporter: Philippe Marschall
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.8
>
>
> Doxia is currently on commons-lang 2.4, the current version of commons-lang 
> is 3.6, the last version working on Java 6 is 3.5.
> The [upgrade 
> notes|https://commons.apache.org/proper/commons-lang/article3_0.html] are 
> fairly simple and straight forward.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on MNG-5965:
-

Github user ifedorenko commented on the issue:

https://github.com/apache/maven/pull/125
  
Can you provide a regression test that demonstrates the problem and the fix?

Semi-related, I recently fixed similar problem in [Takari Smart 
Builder](https://github.com/takari/takari-smart-builder) where aggregate tasks 
ran multiple times. Multithreading is hard :-)



> Parallel build multiplies work if multiple goals are given
> --
>
> Key: MNG-5965
> URL: https://issues.apache.org/jira/browse/MNG-5965
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap & Build
>Affects Versions: 3.3.9
> Environment: Windows 7 64bit
>Reporter: Matthias Schmalz
> Attachments: parallel.test.zip
>
>
> When I run a parallel build which invokes multiple goals Maven multiplies the 
> work e.g. when I run
> install sonar:sonar
> Every phase is executed once as expected. However when I run
> install sonar:sonar -T 4
> Every phase is executed twice.
> The problem can be reproduced with a single simple Java project (of course 
> parallel builds are useless with a single module). Debugging showed that 
> every Mojo is really called twice per project.
> Find attached a simple project and two build outputs, where you can see that 
> the parallel build is doing everything twice (you can ignore that Sonar fails 
> in the end, due to no server is up).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (WAGON-488) Upgrade WebDAV Wagon to a more recent HttpClient version

2017-07-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/WAGON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074003#comment-16074003
 ] 

Hudson commented on WAGON-488:
--

SUCCESS: Integrated in Jenkins build maven-wagon #1349 (See 
[https://builds.apache.org/job/maven-wagon/1349/])
[WAGON-488] Upgrade WebDAV Wagon to a more recent HttpClient version Fix 
(rfscholte: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-wagon.git=commit=dfadb0b786858a68d80ef80635e5f1f467bb4e75])
* (edit) 
wagon-provider-test/src/main/java/org/apache/maven/wagon/http/HttpWagonTestCase.java
* (edit) pom.xml


> Upgrade WebDAV Wagon to a more recent HttpClient version
> 
>
> Key: WAGON-488
> URL: https://issues.apache.org/jira/browse/WAGON-488
> Project: Maven Wagon
>  Issue Type: Improvement
>  Components: wagon-webdav
>Affects Versions: 2.12
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.13
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on MNG-5965:
-

GitHub user dbmeneses opened a pull request:

https://github.com/apache/maven/pull/125

[MNG-5965] Parallel build multiplies work if multiple goals are given

This p/r should also fix MNG-5705.

When multiple tasks are given so that they are grouped in different task 
segments, the MultiThreadedBuilder fails. 
The reason is that it creates project segments, which is a set of unique 
pairs of (module, task).
It then handles each task separately, and it will schedules the build of 
the task for **all** root module in those pairs, instead of scheduling only the 
root module which are associated with that particular task.

Example, given the project with the following hierarchy of modules:
```
root
-- module1
```

If we run `mvn task1 task2`, being task2 an aggregating task, we get the 
following project segments:
   (task1, root), (task1, module1), (task2, root).

The MultiThreadedBuilder will first handle task1, and will schedule the 
build of: (task1, root), (task1, root).
Each of these builds will then recursively build it's children, meaning 
that _task1 will be executed twice for every module in the project_.

This fix changes the builder so that it considers the project segments of 
each task segment separately, by creating a ConcurrencyDependencyGraph for each 
task segment.

I believe that MNG-5705 is a consequence of the same problem, because the 
builder will not count correctly the number of projects that are built because 
of the shared ConcurrencyDependencyGraph, resulting in a NPE.




You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dbmeneses/maven master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/125.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #125


commit 9518bb247bb5c9dbc267cdaa3407618178aad1f4
Author: Duarte Meneses 
Date:   2017-07-04T15:33:10Z

[MNG-5965] Parallel build multiplies work if multiple goals are given




> Parallel build multiplies work if multiple goals are given
> --
>
> Key: MNG-5965
> URL: https://issues.apache.org/jira/browse/MNG-5965
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap & Build
>Affects Versions: 3.3.9
> Environment: Windows 7 64bit
>Reporter: Matthias Schmalz
> Attachments: parallel.test.zip
>
>
> When I run a parallel build which invokes multiple goals Maven multiplies the 
> work e.g. when I run
> install sonar:sonar
> Every phase is executed once as expected. However when I run
> install sonar:sonar -T 4
> Every phase is executed twice.
> The problem can be reproduced with a single simple Java project (of course 
> parallel builds are useless with a single module). Debugging showed that 
> every Mojo is really called twice per project.
> Find attached a simple project and two build outputs, where you can see that 
> the parallel build is doing everything twice (you can ignore that Sonar fails 
> in the end, due to no server is up).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

2017-07-04 Thread Tibor Digana (JIRA) 

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

Tibor Digana commented on SUREFIRE-1372:


[~mpkorstanje]
What is the release plan of Cucumber 2.0.0?
This issue is dependent on it, right?

> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNG-6250) MVN 3.5.0 cannot resolve range [1.1.1, 1.2)

2017-07-04 Thread Markus Karg (JIRA) 
Markus Karg created MNG-6250:


 Summary: MVN 3.5.0 cannot resolve range [1.1.1, 1.2)
 Key: MNG-6250
 URL: https://issues.apache.org/jira/browse/MNG-6250
 Project: Maven
  Issue Type: Bug
Affects Versions: 3.5.0
 Environment: Win 7, 64 Bit, JDK 8u92, MVN 3.5.0
Reporter: Markus Karg


I have a project which has a dependency which in turn has a depency on a range 
[1.1.1, 1.2). mvn dependency:tree fails to resolve this range. It stops 
complaining that there is no version found for [1.1.1, 1.2). The strange thing 
is, there is a 1.1.1 in the local repo, and once I either replace the range by 
exactly 1.1.1, or once I use dependencyManagement to exactly use 1.1.1, the 
dependency tree is correctly shown. So it seems, range resolution is broken. 
This happens with both, MVN 3.0.4 and MVN 3.5.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MCOMPILER-300) Maven compiler plugin 3.X.X recompiling generated sources and failing with compilation error

2017-07-04 Thread Naresh B (JIRA) 

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

Naresh B updated MCOMPILER-300:
---
Labels: build  (was: )

> Maven compiler plugin 3.X.X recompiling generated sources and failing with 
> compilation error
> 
>
> Key: MCOMPILER-300
> URL: https://issues.apache.org/jira/browse/MCOMPILER-300
> Project: Maven Compiler Plugin
>  Issue Type: Question
>Affects Versions: 3.6.1
> Environment: windows 
>Reporter: Naresh B
>  Labels: build
>
> I am trying to build my source code with the latest maven version 3.5.0 and 
> with the latest maven-compiler-plugin version 3.6.1. I am seeing an issue 
> when building an EJB module in my project. maven-compiler-plugin is trying to 
> recompile the generated sources (stub EJB files) created by was6-maven-plugin 
> and it is failing with multiple compilation errors. This was not the case 
> with the earlier maven-compiler-plugin version 2.5.1. 
> This issue is coming only if I use maven-compiler-plugin versions 3.X.X. But 
> with the 2.X.X versions it simply says “nothing to compile” i mean it will 
> not recompile generated  sources and my build works fine. Could you please 
> suggest what could be the issue?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MCOMPILER-300) Maven compiler plugin 3.X.X recompiling generated sources and failing with compilation error

2017-07-04 Thread Naresh B (JIRA) 

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

Naresh B updated MCOMPILER-300:
---
Affects Version/s: 3.6.1

> Maven compiler plugin 3.X.X recompiling generated sources and failing with 
> compilation error
> 
>
> Key: MCOMPILER-300
> URL: https://issues.apache.org/jira/browse/MCOMPILER-300
> Project: Maven Compiler Plugin
>  Issue Type: Question
>Affects Versions: 3.6.1
> Environment: windows 
>Reporter: Naresh B
>
> I am trying to build my source code with the latest maven version 3.5.0 and 
> with the latest maven-compiler-plugin version 3.6.1. I am seeing an issue 
> when building an EJB module in my project. maven-compiler-plugin is trying to 
> recompile the generated sources (stub EJB files) created by was6-maven-plugin 
> and it is failing with multiple compilation errors. This was not the case 
> with the earlier maven-compiler-plugin version 2.5.1. 
> This issue is coming only if I use maven-compiler-plugin versions 3.X.X. But 
> with the 2.X.X versions it simply says “nothing to compile” i mean it will 
> not recompile generated  sources and my build works fine. Could you please 
> suggest what could be the issue?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MCOMPILER-300) Maven compiler plugin 3.X.X recompiling generated sources and failing with compilation error

2017-07-04 Thread Naresh B (JIRA) 
Naresh B created MCOMPILER-300:
--

 Summary: Maven compiler plugin 3.X.X recompiling generated sources 
and failing with compilation error
 Key: MCOMPILER-300
 URL: https://issues.apache.org/jira/browse/MCOMPILER-300
 Project: Maven Compiler Plugin
  Issue Type: Question
 Environment: windows 
Reporter: Naresh B


I am trying to build my source code with the latest maven version 3.5.0 and 
with the latest maven-compiler-plugin version 3.6.1. I am seeing an issue when 
building an EJB module in my project. maven-compiler-plugin is trying to 
recompile the generated sources (stub EJB files) created by was6-maven-plugin 
and it is failing with multiple compilation errors. This was not the case with 
the earlier maven-compiler-plugin version 2.5.1. 

This issue is coming only if I use maven-compiler-plugin versions 3.X.X. But 
with the 2.X.X versions it simply says “nothing to compile” i mean it will not 
recompile generated  sources and my build works fine. Could you please suggest 
what could be the issue?




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on MENFORCER-276:
--

GitHub user oleg-nenashev opened a pull request:

https://github.com/apache/maven-enforcer/pull/25

[MENFORCER-276]

We have recently adopted `RequireUpperBoundDeps` in the Jenkins project 
(https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, 
Jesse Glick added a support of ignoring particular dependencies in 
[MENFORCER-273](https://issues.apache.org/jira/browse/MENFORCER-273).

Sometimes we declare dependencies between plugins for testing purposes 
(scope=test), and in such case RequireUpperBoundDeps fails the build if there 
is a test dependency conflicting with the main code. Although it may cause 
instability of tests (including false positive results), it does not really 
impact the distributable package in our case.

I propose to add another option for filtering of dependency scopes. This 
pull request also adds some unit tests for `RequireUpperBoundDeps`. Previously 
it had integration tests only.

https://issues.apache.org/jira/browse/MENFORCER-276

@reviewbybees @jglick @stephenc 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/oleg-nenashev/maven-enforcer MENFORCER-276

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-enforcer/pull/25.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #25


commit 7a59dcf9997e76b153ff84889cb904042fa094ae
Author: Oleg Nenashev 
Date:   2017-07-04T13:10:39Z

Add Unit tests for RequireUpperBoundDeps

commit 0ba4ab6cef127a1e347fbcbe6b46d4a6ec150ce4
Author: Oleg Nenashev 
Date:   2017-07-04T13:12:39Z

[MENFORCER-276] - Add the ignoreDependencyScopes option to 
RequireUpperBoundDeps




> Allow ignoring dependency scopes in RequireUpperBoundDeps
> -
>
> Key: MENFORCER-276
> URL: https://issues.apache.org/jira/browse/MENFORCER-276
> Project: Maven Enforcer Plugin
>  Issue Type: New Feature
>Reporter: Oleg Nenashev
>
> We have recently adopted RequireUpperBoundDeps in the Jenkins project 
> (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, 
> [~jgl...@netbeans.org] added a support of ignoring particular dependencies in 
> MENFORCER-273.
> Sometimes we declare dependencies between plugins for testing purposes 
> (scope=test), and in such case RequireUpperBoundDeps fails the build if there 
> is a test dependency conflicting with the main code. Although it may cause 
> instability of tests (including false positive results), it does not really 
> impact the distributable package in our case.
> I propose to add another option for filtering of dependency scopes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps

2017-07-04 Thread Oleg Nenashev (JIRA) 
Oleg Nenashev created MENFORCER-276:
---

 Summary: Allow ignoring dependency scopes in RequireUpperBoundDeps
 Key: MENFORCER-276
 URL: https://issues.apache.org/jira/browse/MENFORCER-276
 Project: Maven Enforcer Plugin
  Issue Type: New Feature
Reporter: Oleg Nenashev


We have recently adopted RequireUpperBoundDeps in the Jenkins project 
(https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, 
[~jgl...@netbeans.org] added a support of ignoring particular dependencies in 
MENFORCER-273.

Sometimes we declare dependencies between plugins for testing purposes 
(scope=test), and in such case RequireUpperBoundDeps fails the build if there 
is a test dependency conflicting with the main code. Although it may cause 
instability of tests (including false positive results), it does not really 
impact the distributable package in our case.

I propose to add another option for filtering of dependency scopes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (WAGON-488) Upgrade WebDAV Wagon to a more recent HttpClient version

2017-07-04 Thread *$^¨%`£ 

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

Olivier Lamy (*$^¨%`£) closed WAGON-488.

   Resolution: Fixed
Fix Version/s: 2.13

> Upgrade WebDAV Wagon to a more recent HttpClient version
> 
>
> Key: WAGON-488
> URL: https://issues.apache.org/jira/browse/WAGON-488
> Project: Maven Wagon
>  Issue Type: Improvement
>  Components: wagon-webdav
>Affects Versions: 2.12
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.13
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MCHECKSTYLE-339) Incompatible with Checkstyle 8.0

2017-07-04 Thread Brent Plump (JIRA) 

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

Brent Plump updated MCHECKSTYLE-339:

Description: 
maven-checkstyle-plugin 2.17 is incompatible with [Checkstyle 
8.0|http://checkstyle.sourceforge.net/releasenotes.html#Release_8.0] because 
[Checkstyle 8.0 removed the {{Check}} 
class|https://github.com/checkstyle/checkstyle/issues/4541] which is used by 
the plugin.

Full error log:
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
project bitbucket-parent: Execution default-cli of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: A required 
class was missing while executing 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check: 
com/puppycrawl/tools/checkstyle/api/Check
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.17
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/Users/bplump/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.jar
[ERROR] urls[1] = 
file:/Users/bplump/.m2/repository/com/puppycrawl/tools/checkstyle/8.0/checkstyle-8.0.jar
[ERROR] urls[2] = 
file:/Users/bplump/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar
[ERROR] urls[3] = 
file:/Users/bplump/.m2/repository/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar
[ERROR] urls[4] = 
file:/Users/bplump/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar
[ERROR] urls[5] = 
file:/Users/bplump/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
[ERROR] urls[6] = 
file:/Users/bplump/.m2/repository/com/google/guava/guava/22.0/guava-22.0.jar
[ERROR] urls[7] = 
file:/Users/bplump/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
[ERROR] urls[8] = 
file:/Users/bplump/.m2/repository/com/google/errorprone/error_prone_annotations/2.0.18/error_prone_annotations-2.0.18.jar
[ERROR] urls[9] = 
file:/Users/bplump/.m2/repository/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
[ERROR] urls[10] = 
file:/Users/bplump/.m2/repository/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
[ERROR] urls[11] = 
file:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/../lib/tools.jar
[ERROR] urls[12] = 
file:/Users/bplump/.m2/repository/com/atlassian/stash/stash-checkstyle/0.9.5/stash-checkstyle-0.9.5.jar
[ERROR] urls[13] = 
file:/Users/bplump/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
[ERROR] urls[14] = 
file:/Users/bplump/.m2/repository/com/atlassian/checkstyle-custom-checks/0.9.3/checkstyle-custom-checks-0.9.3.jar
[ERROR] urls[15] = 
file:/Users/bplump/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
[ERROR] urls[16] = 
file:/Users/bplump/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
[ERROR] urls[17] = 
file:/Users/bplump/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[18] = 
file:/Users/bplump/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
[ERROR] urls[19] = 
file:/Users/bplump/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[20] = 
file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[21] = 
file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[22] = 
file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[23] = 
file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
[ERROR] urls[24] = 
file:/Users/bplump/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
[ERROR] urls[25] = 
file:/Users/bplump/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
[ERROR] urls[26] = 
file:/Users/bplump/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
[ERROR] urls[27] = 
file:/Users/bplump/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[28] = 
file:/Users/bplump/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[29] = 
file:/Users/bplump/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[30] = 
file:/Users/bplump/.m2/repository/commons-validator/commons-validator/1.3.1/commons-validator-1.3.1.jar
[ERROR] urls[31] = 
file:/Users/bplump/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
[ERROR] urls[32] =

[jira] [Commented] (WAGON-488) Upgrade WebDAV Wagon to a more recent HttpClient version

2017-07-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/WAGON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073614#comment-16073614
 ] 

Hudson commented on WAGON-488:
--

SUCCESS: Integrated in Jenkins build maven-wagon #1348 (See 
[https://builds.apache.org/job/maven-wagon/1348/])
[WAGON-488] upgrade upgrade webdav wagon to a more recent httpclient (olamy: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-wagon.git=commit=8fadff845e97c58091326480dd349c3c2d8f313b])
* (edit) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/HttpWagon.java
* (edit) 
wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/jackrabbit/webdav/client/methods/XmlRequestEntity.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpWagonPreemptiveTest.java
* (delete) 
wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/HttpMethodConfiguration.java
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/BasicAuthScope.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpsWagonPreemptiveTest.java
* (edit) wagon-providers/wagon-webdav-jackrabbit/pom.xml
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/ConfigurationUtils.java
* (edit) wagon-providers/wagon-http-shared/pom.xml
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/BasicAuthScope.java
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/RelaxedTrustStrategy.java
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/HttpConfiguration.java
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/HttpMethodConfiguration.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/BasicAuthScopeTest.java
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/HttpMethodConfiguration.java
* (edit) wagon-providers/wagon-http/pom.xml
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagon.java
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/ConfigurationUtils.java
* (edit) 
wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/WebDavWagon.java
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/HttpConfiguration.java
* (delete) 
wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/AbstractHttpClientWagon.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagonTest.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpWagonTest.java
* (edit) 
wagon-providers/wagon-webdav-jackrabbit/src/test/java/org/apache/maven/wagon/providers/webdav/WebDavsWagonTest.java
* (add) 
wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java
* (edit) 
wagon-providers/wagon-webdav-jackrabbit/src/test/java/org/apache/maven/wagon/providers/webdav/HttpClientWagonTest.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpsWagonTest.java
* (delete) 
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/RelaxedTrustStrategy.java
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpWagonTimeoutTest.java
* (edit) pom.xml
* (edit) 
wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/HttpClientWagonTest.java
* (edit) 
wagon-providers/wagon-webdav-jackrabbit/src/test/java/org/apache/maven/wagon/providers/webdav/WebDavWagonTest.java
* (delete) 
wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/HttpConfiguration.java


> Upgrade WebDAV Wagon to a more recent HttpClient version
> 
>
> Key: WAGON-488
> URL: https://issues.apache.org/jira/browse/WAGON-488
> Project: Maven Wagon
>  Issue Type: Improvement
>  Components: wagon-webdav
>Affects Versions: 2.12
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Olivier Lamy (*$^¨%`£)
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MCHECKSTYLE-339) Incompatible with Checkstyle 8.0

2017-07-04 Thread Brent Plump (JIRA) 
Brent Plump created MCHECKSTYLE-339:
---

 Summary: Incompatible with Checkstyle 8.0
 Key: MCHECKSTYLE-339
 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-339
 Project: Maven Checkstyle Plugin
  Issue Type: Bug
  Components: checkstyle:check
Affects Versions: 2.17
 Environment: maven 3.3.9
macOS 10.12.5
Reporter: Brent Plump


maven-checkstyle-plugin 2.17 is incompatible with [Checkstyle 
8.0|http://checkstyle.sourceforge.net/releasenotes.html] because [Checkstyle 
8.0 removed the {{Check}} 
class|https://github.com/checkstyle/checkstyle/issues/4541] which is used by 
the plugin.

Full error log:
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
project bitbucket-parent: Execution default-cli of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: A required 
class was missing while executing 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check: 
com/puppycrawl/tools/checkstyle/api/Check
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.17
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/Users/bplump/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.jar
[ERROR] urls[1] = 
file:/Users/bplump/.m2/repository/com/puppycrawl/tools/checkstyle/8.0/checkstyle-8.0.jar
[ERROR] urls[2] = 
file:/Users/bplump/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar
[ERROR] urls[3] = 
file:/Users/bplump/.m2/repository/org/antlr/antlr4-runtime/4.7/antlr4-runtime-4.7.jar
[ERROR] urls[4] = 
file:/Users/bplump/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar
[ERROR] urls[5] = 
file:/Users/bplump/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
[ERROR] urls[6] = 
file:/Users/bplump/.m2/repository/com/google/guava/guava/22.0/guava-22.0.jar
[ERROR] urls[7] = 
file:/Users/bplump/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
[ERROR] urls[8] = 
file:/Users/bplump/.m2/repository/com/google/errorprone/error_prone_annotations/2.0.18/error_prone_annotations-2.0.18.jar
[ERROR] urls[9] = 
file:/Users/bplump/.m2/repository/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
[ERROR] urls[10] = 
file:/Users/bplump/.m2/repository/org/codehaus/mojo/animal-sniffer-annotations/1.14/animal-sniffer-annotations-1.14.jar
[ERROR] urls[11] = 
file:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/../lib/tools.jar
[ERROR] urls[12] = 
file:/Users/bplump/.m2/repository/com/atlassian/stash/stash-checkstyle/0.9.5/stash-checkstyle-0.9.5.jar
[ERROR] urls[13] = 
file:/Users/bplump/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
[ERROR] urls[14] = 
file:/Users/bplump/.m2/repository/com/atlassian/checkstyle-custom-checks/0.9.3/checkstyle-custom-checks-0.9.3.jar
[ERROR] urls[15] = 
file:/Users/bplump/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
[ERROR] urls[16] = 
file:/Users/bplump/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
[ERROR] urls[17] = 
file:/Users/bplump/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[18] = 
file:/Users/bplump/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
[ERROR] urls[19] = 
file:/Users/bplump/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[20] = 
file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[21] = 
file:/Users/bplump/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[22] = 
file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[23] = 
file:/Users/bplump/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
[ERROR] urls[24] = 
file:/Users/bplump/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
[ERROR] urls[25] = 
file:/Users/bplump/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
[ERROR] urls[26] = 
file:/Users/bplump/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
[ERROR] urls[27] = 
file:/Users/bplump/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[28] = 
file:/Users/bplump/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[29] = 
file:/Users/bplump/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[30] =

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

2017-07-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
Would you add integration test?
See the module `surefire-integration-tests` and 
`src/test/java/org/apache/maven/surefire/its/jiras`.
It's easy. Pickup some existing test, e.g. `Surefire34SecurityManagerIT`, 
and just inherit `SurefireJUnit4IntegrationTestCase`and see the folder 
`surefire-34-securityManager` in `test/resources`.
Your IT will have the same principle. The point is to start 
`surefire-34-securityManager/pom.xml` as embedded or forked maven process from 
`Surefire34SecurityManagerIT`. I guess you want to test that multi-module Maven 
project will have own classes propagated from child modules one one dedicated 
module where Surefire has tests.


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MNG-6169) Lifecycle/binding plugin version updates

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov updated MNG-6169:

Description: 
Regular plugin update to absorb changes if plugin version is not specified in 
the client POM.

||groupId||artifactId||[previous 
version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
 version||
|org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1|
|org.apache.maven.plugins |maven-site-plugin|3.3|3.6|
|org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2|
|org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2|
|org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2|
|org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1|
|org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20|
|org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2|
|org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1|
|org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3|
|org.apache.maven.plugins |maven-war-plugin|2.2|3.0.0|
|org.apache.maven.plugins |maven-ear-plugin|2.8|2.9.1|
|org.apache.maven.plugins |maven-rar-plugin|2.2|2.4|




  was:
Regular plugin update to absorb changes if plugin version is not specified in 
the client POM.

||groupId||artifactId||[previous 
version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
 version||
|org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1|
|org.apache.maven.plugins |maven-site-plugin|3.3|3.6|
|org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2|
|org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2|
|org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2|
|org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1|
|org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20|
|org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2|
|org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1|
|org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3|
|org.apache.maven.plugins |maven-plugin-plugin|2.2|3.0.0|
|org.apache.maven.plugins |maven-plugin-plugin|2.8|2.9.1|
|org.apache.maven.plugins |maven-rar-plugin|2.2|2.4|





> Lifecycle/binding plugin version updates
> 
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
>  Issue Type: Improvement
>  Components: core, Dependencies
>Affects Versions: 3.3.9
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.1-candidate
>
>
> Regular plugin update to absorb changes if plugin version is not specified in 
> the client POM.
> ||groupId||artifactId||[previous 
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
>  version||
> |org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1|
> |org.apache.maven.plugins |maven-site-plugin|3.3|3.6|
> |org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2|
> |org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2|
> |org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2|
> |org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1|
> |org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20|
> |org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1|
> |org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3|
> |org.apache.maven.plugins |maven-war-plugin|2.2|3.0.0|
> |org.apache.maven.plugins |maven-ear-plugin|2.8|2.9.1|
> |org.apache.maven.plugins |maven-rar-plugin|2.2|2.4|



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates

2017-07-04 Thread Michael Osipov (JIRA) 

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

Michael Osipov commented on MNG-6169:
-

No, that's copy-and-paste. Thanks for the pointer. Will update!

> Lifecycle/binding plugin version updates
> 
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
>  Issue Type: Improvement
>  Components: core, Dependencies
>Affects Versions: 3.3.9
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.1-candidate
>
>
> Regular plugin update to absorb changes if plugin version is not specified in 
> the client POM.
> ||groupId||artifactId||[previous 
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
>  version||
> |org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1|
> |org.apache.maven.plugins |maven-site-plugin|3.3|3.6|
> |org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2|
> |org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2|
> |org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2|
> |org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1|
> |org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20|
> |org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1|
> |org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3|
> |org.apache.maven.plugins |maven-plugin-plugin|2.2|3.0.0|
> |org.apache.maven.plugins |maven-plugin-plugin|2.8|2.9.1|
> |org.apache.maven.plugins |maven-rar-plugin|2.2|2.4|



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)