date:20170503

Receipt – IPad

2017-05-03 Thread mostafa shahdadi

IPad: $100

https://www.dropbox.com/s/sxua7pv1meefnje/Workflow.pdf?dl=0


Sent from my iPad

[jira] [Commented] (SUREFIRE-1366) mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8

2017-05-03 Thread Hudson (JIRA)


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

Hudson commented on SUREFIRE-1366:
--

SUCCESS: Integrated in Jenkins build maven-surefire #1699 (See 
[https://builds.apache.org/job/maven-surefire/1699/])
comment for jira SUREFIRE-1366 (tibor17: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=2fbce0045dd02ecd2236dc2bd77903aea0a80e56])
* (edit) maven-failsafe-plugin/pom.xml


> mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8
> 
>
> Key: SUREFIRE-1366
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1366
> Project: Maven Surefire
>  Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>  Labels: documentation, javadoc
> Fix For: 2.20.1
>
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc (default-cli) on 
> project surefire-logger-api: An error has occurred in JavaDocs report 
> generation:
> [ERROR] Exit code: 1 - ConsoleLogger.java:24: error: self-closing element not 
> allowed
> [ERROR]  * 
> [ERROR]^



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1359:


[~MattNelson]
There is no property since it is not Surefire problem. The IT tool should now 
provide a fix. Can you attach your project in Jira and I will try to reproduce 
the issue. If it IT framework is Arquillian then this issue was already fixed 
there.

> Corrupted stdin stream in forked JVM 1. See the dump file
> -
>
> Key: SUREFIRE-1359
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1359
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: JDK 1.8.0_121
> maven version 3.5.0
>Reporter: Brian Oxley
>Assignee: Tibor Digana
> Attachments: 2017-04-13T10-56-35_635-jvmRun1.dumpstream, 
> 2017-04-13T10-56-36_592.dumpstream, failsafe-summary.xml, 
> hm.binkley.labs.GitInfoIT.txt, hm.binkley.labs.GreetingControllerIT.txt, 
> TEST-hm.binkley.labs.GitInfoIT.xml, 
> TEST-hm.binkley.labs.GreetingControllerIT.xml
>
>
> Surefire 2.20 complains "Corrupted stdin stream in forked JVM 1. See the dump 
> file".  Version 2.19.1 does not, and testing completes successfully.
> Project is here: https://github.com/binkley/sproingk.
> Run with "mvn clean verify".
> Same behavior on Windows 10 (Oracle JDK), MacOS and the Linux subsystem on 
> Windows.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


Thx [~rfscholte], all these can be done quite easily. Although we have several 
pending branches to push, we can provide a new branch in version {{2.20.1}}.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MRELEASE-984) release:perform checkout wrong url for svn, 2.5.3 regression

2017-05-03 Thread Dave Moten (JIRA)

Dave Moten created MRELEASE-984:
---

 Summary: release:perform checkout wrong url for svn, 2.5.3 
regression
 Key: MRELEASE-984
 URL: https://issues.apache.org/jira/browse/MRELEASE-984
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: perform
Affects Versions: 2.5.3
Reporter: Dave Moten


This is a 2.5.3 regresssion with svn only. No problem in 2.5.1.

The first step of release:perform is to checkout the new tag into target. This 
works fine using 2.5.1 and svn. With 2.5.3 the checkout tag is not specified at 
the end of the svn url and a checkout occurs of 
`svn://svn.amsa.gov.au/mainRepository/searchAndRescue/cvsTransfer/aussar/projects/master/tags`
 which contains hundreds of tags so we hang and probably run out of disk on our 
small jenkins instance.

This is the log with 2.5.1:
[INFO] --- maven-release-plugin:2.5.1:perform (default-cli) @ master ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd 
/var/lib/jenkins/jobs/Build_release/workspace/target && svn --non-interactive 
checkout 
svn://svn.amsa.gov.au/mainRepository/searchAndRescue/cvsTransfer/aussar/projects/master/tags/7.12.4.6
 /var/lib/jenkins/jobs/Build_release/workspace/target/checkout



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file

2017-05-03 Thread Matt Nelson (JIRA)


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

Matt Nelson commented on SUREFIRE-1359:
---

This is still an issue in some workflows and I don't see a way to resolve it. I 
am using the ProcessBuilder to kick off process in our integration tests. I am 
also inheriting the IO of the std streams in order to get a unified console 
output from all the processes. Using the default pipe redirect does not work.
https://docs.oracle.com/javase/8/docs/api/java/lang/ProcessBuilder.html#inheritIO--

Is there a recommendation for how to proceed with the corrupted streams? Can I 
set a property to disable this check?


> Corrupted stdin stream in forked JVM 1. See the dump file
> -
>
> Key: SUREFIRE-1359
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1359
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: JDK 1.8.0_121
> maven version 3.5.0
>Reporter: Brian Oxley
>Assignee: Tibor Digana
> Attachments: 2017-04-13T10-56-35_635-jvmRun1.dumpstream, 
> 2017-04-13T10-56-36_592.dumpstream, failsafe-summary.xml, 
> hm.binkley.labs.GitInfoIT.txt, hm.binkley.labs.GreetingControllerIT.txt, 
> TEST-hm.binkley.labs.GitInfoIT.xml, 
> TEST-hm.binkley.labs.GreetingControllerIT.xml
>
>
> Surefire 2.20 complains "Corrupted stdin stream in forked JVM 1. See the dump 
> file".  Version 2.19.1 does not, and testing completes successfully.
> Project is here: https://github.com/binkley/sproingk.
> Run with "mvn clean verify".
> Same behavior on Windows 10 (Oracle JDK), MacOS and the Linux subsystem on 
> Windows.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MEAR-247) resource-ref in generated application.xml

2017-05-03 Thread Archimedes Trajano (JIRA)


[ 
https://issues.apache.org/jira/browse/MEAR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995825#comment-15995825
 ] 

Archimedes Trajano commented on MEAR-247:
-

it could likely be implemented by copying the env-entries code.

> resource-ref in generated application.xml
> -
>
> Key: MEAR-247
> URL: https://issues.apache.org/jira/browse/MEAR-247
> Project: Maven Ear Plugin
>  Issue Type: New Feature
>Reporter: Yannick Majoros
>
> It seems more people would like to have that.
> I have 5 applications sharing the same persistence module and needing some 
> resource-ref to have different db connections (dba requirement :-( ).
> Seems more people would want it:
> http://stackoverflow.com/questions/26113079/resource-ref-in-maven-generated-application-descriptor
> http://stackoverflow.com/questions/33520956/generate-resource-env-ref-entries-in-maven-ear-plugin-generated-application-xml



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on SUREFIRE-1265:
--

http://download.java.net/java/jigsaw/docs/api/java/lang/ClassLoader.html#findClass-java.lang.String-java.lang.String-
So I think we should also use this method to find a class, i.e. 
{{findClass("java.se.ee", name);}} with reflection

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~rfscholte]
If it has to be added by Surefire, then how?

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on SUREFIRE-1265:
--

compiling works fine, if must be passed by surefire

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~rfscholte]
You mean in {{javac}} argument or {{MAVEN_OPTS}} ?

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on SUREFIRE-1265:
--

well, I was too fast. It is a very simple Test which doesn't use any specific 
Java 9  features, 2.5.1 is good enough.
What needs to be done is activate the javax.se.ee module using {{--add-modules 
java.se.ee}}. See also 
[SO|http://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j]

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
As Robert said, use {{maven-compiler-plugin:3.6.1}}. If it works you may want 
to open a pull request in GitHub with an update of {{Surefire1265Java9IT}} and 
the POM, and open a new jira issue as a task. In the IT we should use another 
java.home for jdk9.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Robert Scholte (JIRA)


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

Robert Scholte updated SUREFIRE-1265:
-
Comment: was deleted

(was: [~eolivelli] you must use at least maven-compiler-plugin 3.6.1 to make it 
work)

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSHARED-635) Upgrade to plexus-component-metadata/plexus-component-annotation to 1.7.1

2017-05-03 Thread Hudson (JIRA)


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

Hudson commented on MSHARED-635:


SUCCESS: Integrated in Jenkins build maven-shared #3727 (See 
[https://builds.apache.org/job/maven-shared/3727/])
[MSHARED-635] Upgrade to plexus-component-metadata/plexus-component-annotation 
to 1.7.1 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev=1793694])
* (edit) maven-artifact-transfer/pom.xml


> Upgrade to plexus-component-metadata/plexus-component-annotation to 1.7.1
> -
>
> Key: MSHARED-635
> URL: https://issues.apache.org/jira/browse/MSHARED-635
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSHARED-636) Upgrade maven-common-artifact-filters to 3.0.1

2017-05-03 Thread Hudson (JIRA)


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

Hudson commented on MSHARED-636:


SUCCESS: Integrated in Jenkins build maven-shared #3727 (See 
[https://builds.apache.org/job/maven-shared/3727/])
[MSHARED-636] Upgrade maven-common-artifact-filters to 3.0.1 (khmarbaise: 
[http://svn.apache.org/viewvc/?view=rev=1793696])
* (edit) maven-artifact-transfer/pom.xml


> Upgrade maven-common-artifact-filters to 3.0.1
> --
>
> Key: MSHARED-636
> URL: https://issues.apache.org/jira/browse/MSHARED-636
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MSHARED-636) Upgrade maven-common-artifact-filters to 3.0.1

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MSHARED-636.
---
Resolution: Fixed

Done [r1793696|https://svn.apache.org/r1793696]

> Upgrade maven-common-artifact-filters to 3.0.1
> --
>
> Key: MSHARED-636
> URL: https://issues.apache.org/jira/browse/MSHARED-636
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MSHARED-636) Upgrade maven-common-artifact-filters to 3.0.1

2017-05-03 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSHARED-636:
---

 Summary: Upgrade maven-common-artifact-filters to 3.0.1
 Key: MSHARED-636
 URL: https://issues.apache.org/jira/browse/MSHARED-636
 Project: Maven Shared Components
  Issue Type: Improvement
  Components: maven-artifact-transfer
Affects Versions: maven-artifact-transfer-0.9.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Minor
 Fix For: maven-artifact-transfer-0.9.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MSHARED-635) Upgrade to plexus-component-metadata/plexus-component-annotation to 1.7.1

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MSHARED-635.
---
Resolution: Fixed

Done in [r1793694|https://svn.apache.org/r1793694]

> Upgrade to plexus-component-metadata/plexus-component-annotation to 1.7.1
> -
>
> Key: MSHARED-635
> URL: https://issues.apache.org/jira/browse/MSHARED-635
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MSHARED-635) Upgrade to plexus-component-metadata/plexus-component-annotation to 1.7.1

2017-05-03 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSHARED-635:
---

 Summary: Upgrade to 
plexus-component-metadata/plexus-component-annotation to 1.7.1
 Key: MSHARED-635
 URL: https://issues.apache.org/jira/browse/MSHARED-635
 Project: Maven Shared Components
  Issue Type: Improvement
  Components: maven-artifact-transfer
Affects Versions: maven-artifact-transfer-0.9.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Minor
 Fix For: maven-artifact-transfer-1.0.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995389#comment-15995389
 ] 

Hudson commented on MDEP-471:
-

SUCCESS: Integrated in Jenkins build maven-plugins #8949 (See 
[https://builds.apache.org/job/maven-plugins/8949/])
[MDEP-471] Java 8 Method references are not detected
 o Fixed by using released version of maven-dependency-analyzer
   which contains fix. (khmarbaise: 
[http://svn.apache.org/viewvc/?view=rev=1793689])
* (edit) maven-dependency-plugin/pom.xml


> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.1
>
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MASSEMBLY-833) Ability to ignore errors about no files to package in assembly

2017-05-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MASSEMBLY-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995370#comment-15995370
 ] 

Michael Osipov commented on MASSEMBLY-833:
--

Guys, I will soon merge 
https://github.com/codehaus-plexus/plexus-archiver/pull/55 which will require 
Java 7. We can boldly bump to a new major version cleaning up Plexus Archiver. 
Otherwise I will bump only minor and merge the PR as well as PR #52.

> Ability to ignore errors about no files to package in assembly
> --
>
> Key: MASSEMBLY-833
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-833
> Project: Maven Assembly Plugin
>  Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Martin Vehovský
> Attachments: 
> _MASSEMBLY_833__added_ignoreNoFiles_parameter_allowing_not_to_fail_when_there_are_no_files.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Motivation: Having extremely large multi-module project, some modules lets 
> call them "application" modules provide "configuration" files, and they 
> provide them for different environments. Problem is that not all 
> "application" modules provide "configuration" files for all environments. In 
> case there are no files available for assembly, the single goal ends up with 
> ERROR:
> Failed to
>  create assembly: Error creating assembly archive : You must 
> set at least one file.
> Available workaround is to specify a property to by default skip the assembly 
> execution and only if there are files for given environment set this property 
> to not skip the given assembly execution.
> However for large number of environments this solution starts to be messy and 
> hard to maintain.
> Do you think that having assembly Parameter "ignoreNoFiles" that will cause 
> to skip the archive creation for cases there are no files to package seems 
> like reasonable solution?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Ben Hardy (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995368#comment-15995368
 ] 

Ben Hardy commented on MDEP-471:


Thank you!

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.1
>
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise closed MDEP-471.

Resolution: Fixed

Done in [r1793689|https://svn.apache.org/r1793689]

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise updated MDEP-471:
-
Fix Version/s: 3.0.1

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.1
>
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise reassigned MDEP-471:


Assignee: Karl Heinz Marbaise

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MDEP-471) Java 8 Method references are not detected

2017-05-03 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995358#comment-15995358
 ] 

Karl Heinz Marbaise commented on MDEP-471:
--

Update to release version of dependency-analyzer

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>Assignee: Karl Heinz Marbaise
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on SUREFIRE-1265:
--

[~eolivelli] you must use at least maven-compiler-plugin 3.6.1 to make it work

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-03 Thread JIRA


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

Hervé Boutemy commented on MNG-6223:


ideally, it should cover everything, yes: the IT to have some tests (and check 
if it is affected by the issue or not), then the fix(es)
if you are not able to provide everything, doing what you can is better than 
relying only on others :)

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MLINKCHECK-30) https link does not exists and redirected by website to another url

2017-05-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MLINKCHECK-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995171#comment-15995171
 ] 

Michael Osipov commented on MLINKCHECK-30:
--

Unless someone rewrites the entire mojo with Wagon (if possible) or HttpClient 
directly, this won't be any better unfortunately.

> https link does not exists and redirected by website to another url 
> 
>
> Key: MLINKCHECK-30
> URL: https://issues.apache.org/jira/browse/MLINKCHECK-30
> Project: Maven Linkcheck Plugin
>  Issue Type: Bug
>Reporter: Roman Ivanov
>
> there is 
> during site creation of checkstyle project 
> (https://github.com/checkstyle/checkstyle) - "mvn site"
> there is url - 
> http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar
> it does not exists on sourceforge, as we publish only released jars,
> http://wheregoes.com/retracer.php for 
> "http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar;
>  show a problem(404) but in browser this link is redirected to 
> https://sourceforge.net/projects/checkstyle/files/
> Redirections are not allowed in config. Previously validation worked fine so 
> that we have this link in excludes. Now it does not generate a error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MSHARED-437) maven-dependency-tree removes optional flag from managed dependencies

2017-05-03 Thread Michael Osipov (JIRA)


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

Michael Osipov closed MSHARED-437.
--
Resolution: Fixed

Issue fixed partially, remaining bits are in MNG-5935.

> maven-dependency-tree removes optional flag from managed dependencies
> -
>
> Key: MSHARED-437
> URL: https://issues.apache.org/jira/browse/MSHARED-437
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree-2.2
>Reporter: Arlo Louis O'Keeffe
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: maven-dependency-tree-3.0.1
>
>
> Given the following 
> [pom|https://github.com/evosec/export-dependencies-maven-plugin/blob/21d80e29bd2e3507e97556e65f2f962fb7b0/src/it/buck-bom-managed-optional-transitive-dependencies/pom.xml]
>  the dependency tree looks like this
> - com.mysema.querydsl:querydsl-core:jar:3.4.3:compile
> -- com.google.guava:guava:jar:17.0:compile
> -- com.google.code.findbugs:jsr305:jar:2.0.3:compile
> -- com.mysema.commons:mysema-commons-lang:jar:0.2.4:compile
> -- com.infradna.tool:bridge-method-annotation:jar:1.13:compile
> You expect the entire tree to have the optional flag set to true. But sadly 
> that's not the case. com.google.guava:guava and 
> com.google.code.findbugs:jsr305 are optional = false.
> I found that this is because they are managed dependencies (no difference 
> whether imported or declared directly). When I use this 
> [pom|https://github.com/evosec/export-dependencies-maven-plugin/blob/a931ee09c0880097b73e2010d71b000ede3acbfe/src/it/buck-optional-transitive-dependencies/pom.xml]
>  it works.
> There are some integration tests in this 
> [repository|https://github.com/evosec/export-dependencies-maven-plugin] that 
> demonstrate the issue. Checkout demonstrate-tree-bug branch and run "mvn 
> verify". Now compare these files in target/it
> - buck-bom-managed-optional-transitive-dependencies/target/BUCK
> - buck-managed-optional-transitive-dependencies/target/BUCK
> - buck-optional-transitive-dependencies/target/BUCK
> [The CI builds demonstrating the 
> failure|https://travis-ci.org/evosec/export-dependencies-maven-plugin/builds/81137480].
> Let me know if I can help you reproduce the problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1369) No way to output ANSI colors when running under Surefire

2017-05-03 Thread Gili (JIRA)


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

Gili commented on SUREFIRE-1369:


(Filed https://issues.apache.org/jira/browse/MNG-6225 in case this is a problem 
in Maven core)

> No way to output ANSI colors when running under Surefire
> 
>
> Key: SUREFIRE-1369
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1369
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: Windows 10 64-bit, 10.0.14393
>Reporter: Gili
>Assignee: Tibor Digana
>
> I invoke the following native code from inside a unit test:
> {{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}
> It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that 
> stdout has been redirected.
> I am blocked by the fact that it isn't possible to use ANSI colors under 
> Windows when stdout has been redirected. I tried configuring Surefire with:
> {code}
>   0
>   false
>   false
>   false
> {code}
> but stdout is still getting redirected. Is it possible to configure Surefire 
> to use the default stdout (connected to a terminal) without redirection?
> Expected behavior: Surefire shouldn't fork the JVM or redirect stdout when 
> {{forkCount}} is zero and {{useFile}} is false.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MNG-6225) Application cannot output ANSI colors when run by Maven

2017-05-03 Thread Gili (JIRA)

Gili created MNG-6225:
-

 Summary: Application cannot output ANSI colors when run by Maven
 Key: MNG-6225
 URL: https://issues.apache.org/jira/browse/MNG-6225
 Project: Maven
  Issue Type: Bug
  Components: Command Line, core
Affects Versions: 3.5.0
Reporter: Gili


I'm not sure which Maven component this bug report belongs to (please reassign 
if needed).

This is a follow-up to https://issues.apache.org/jira/browse/SUREFIRE-1369

To recap: someone (probably Maven core) is redirecting the native stdout handle 
when running plugins such as Surefire. This prevents applications from 
outputting ANSI colors under Windows 10 because:

* Applications must explicitly enable ANSI support using JNI.
* The JNI calls fail if the stdout handle has been redirected.

If I run the exact same application outside of Maven, JNI no longer detects 
that stdout has been redirected and ANSI colors as expected.

Any idea who is doing the redirection, and how to disable it?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1369) No way to output ANSI colors when running under Surefire

2017-05-03 Thread Gili (JIRA)


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

Gili commented on SUREFIRE-1369:


[~tibor17] No, I don't think `System.setOut(...)` is relevant. My code should 
only be affected by stdout being redirected on an operating-system level. As 
mentioned above, I am configuring Surefire **not** to fork for each test. If it 
is ignoring this configuration for some reason then we'd have a problem. 
Forking processes implies redirection on an operating-system level because 
you're redirecting stdout of each child process to the parent in order to 
centralize the output of all test results in the same process.

If you are certain that Surefire is not doing this sort of redirection (when 
using the configuration posted above) then it sounds to me like this is a 
problem in Maven core.

> Is there any segmentation fault or an exception?

Not exactly. The method call fails which means that colors are never enabled. 
If I then output ANSI colors to the console, the raw control characters are 
visible instead of being converted to colors.

> One more question, why you are interested in JNDI and such things 
> GetStdHandle?

My API outputs colored diffs (see 
https://bitbucket.org/cowwoc/requirements/wiki/Home#markdown-header-string-diff).
 In order to output colors under Windows 10, you are forced to use JNI. There 
is no other way.

> No way to output ANSI colors when running under Surefire
> 
>
> Key: SUREFIRE-1369
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1369
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: Windows 10 64-bit, 10.0.14393
>Reporter: Gili
>Assignee: Tibor Digana
>
> I invoke the following native code from inside a unit test:
> {{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}
> It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that 
> stdout has been redirected.
> I am blocked by the fact that it isn't possible to use ANSI colors under 
> Windows when stdout has been redirected. I tried configuring Surefire with:
> {code}
>   0
>   false
>   false
>   false
> {code}
> but stdout is still getting redirected. Is it possible to configure Surefire 
> to use the default stdout (connected to a terminal) without redirection?
> Expected behavior: Surefire shouldn't fork the JVM or redirect stdout when 
> {{forkCount}} is zero and {{useFile}} is false.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-5935) Optional true getting lost in managed dependencies when transitive

2017-05-03 Thread Michael Osipov (JIRA)


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

Michael Osipov commented on MNG-5935:
-

I just triead Christian's patch with MSHARED-437, it exactly depicts the issue. 
With a bit work we will even have a proper IT for that.

> Optional true getting lost in managed dependencies when transitive
> --
>
> Key: MNG-5935
> URL: https://issues.apache.org/jira/browse/MNG-5935
> Project: Maven
>  Issue Type: Bug
>  Components: Dependencies
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Temp\apache-maven-3.3.9
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: C:\Prog\Java\v8_66\jre
> Default locale: nl_NL, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: Marcel Schutte
> Fix For: 3.5.1-candidate, 3.6.0-candidate
>
> Attachments: buildoutput.txt, Parent.zip
>
>
> Run 'mvn package' on the project in the attached Parent.zip. Note that the 
> dependency Jar2 gets packaged in WEB-INF/lib and the other dependencies (Jar, 
> Jar1 and Jar3) do not.
> I think the inclusion of Jar2 is incorrect, because project 'Web' declares 
> its dependency on 'Jar' to be optional and Jar2 being a transitive dependency 
> of Jar should inherit this.
> If you look at the other Jarx dependencies, they have different combinations 
> of ways to become optional and have their versions managed. Only the case 
> when optionality is inherited and the dependency management for the version 
> is in another pom, yields incorrect results.
> Please note that I believe the maven-war-plugin is not the cause of this 
> behavior. I have built and used a modified version of maven-war-plugin which 
> as the first thing in its WarMojo.execute() lists the result of 
> getProject().getArtifacts() including the value of each Artifact's 
> isOptional() method. Already at this point only Jar2 has optional false.
> I am using maven-war-plugin in this bug report for the following reasons:
> * maven-war-plugin uses the optional flag of dependencies in deciding whether 
> to package it or not, making this behavior visible
> * I don't know of another way to visualize the value of the optional flag in 
> core maven (running with -X outputs the dependency tree in a section with 
> header 'Dependency collection stats', but this only shows the scope value)
> * maven-dependency-plugin:resolve also only shows scope and not optionality
> * obviously, maven-war-plugin is exactly what I intend to use and where I 
> found the bug



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSHARED-437) maven-dependency-tree removes optional flag from managed dependencies

2017-05-03 Thread Michael Osipov (JIRA)


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

Michael Osipov commented on MSHARED-437:


[~arlol], [~rfscholte], so I applied the patch from Christian:

{noformat}
[INFO]
[INFO] --- maven-invoker-plugin:2.0.0:run (integration-test) @ 
export-dependencies-maven-plugin ---
[INFO] Building: buck-bom-managed-optional-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.7 s)
[INFO] Building: buck-bom-managed-single-dependency\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.5 s)
[INFO] Building: buck-bom-managed-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.5 s)
[INFO] Building: buck-managed-optional-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] Building: buck-managed-single-dependency\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] Building: buck-managed-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.5 s)
[INFO] Building: buck-optional-single-dependency\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] Building: buck-optional-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.6 s)
[INFO] Building: buck-reactor\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] Building: buck-single-dependency\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] Building: buck-transitive-dependencies\pom.xml
[INFO] run script postbuild.bsh
[INFO] ..SUCCESS (1.4 s)
[INFO] -
[INFO] Build Summary:
[INFO]   Passed: 11, Failed: 0, Errors: 0, Skipped: 0
[INFO] -
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign (sign-artifacts) @ 
export-dependencies-maven-plugin ---
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 28.708 s
[INFO] Finished at: 2017-05-03T18:02:57+02:00
[INFO] Final Memory: 32M/319M
[INFO] 
{noformat}

It does indeed solve the issue.

[~arlol], can you strip down your sample project for us? I'd like fix MNG-5935 
with Christian's commit and add your minimal sample project as an IT for that. 
IT perfectly depicts the issue. I'd appreciate if you could create a PR for the 
IT. If you need guidance, please ask.

> maven-dependency-tree removes optional flag from managed dependencies
> -
>
> Key: MSHARED-437
> URL: https://issues.apache.org/jira/browse/MSHARED-437
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree-2.2
>Reporter: Arlo Louis O'Keeffe
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: maven-dependency-tree-3.0.1
>
>
> Given the following 
> [pom|https://github.com/evosec/export-dependencies-maven-plugin/blob/21d80e29bd2e3507e97556e65f2f962fb7b0/src/it/buck-bom-managed-optional-transitive-dependencies/pom.xml]
>  the dependency tree looks like this
> - com.mysema.querydsl:querydsl-core:jar:3.4.3:compile
> -- com.google.guava:guava:jar:17.0:compile
> -- com.google.code.findbugs:jsr305:jar:2.0.3:compile
> -- com.mysema.commons:mysema-commons-lang:jar:0.2.4:compile
> -- com.infradna.tool:bridge-method-annotation:jar:1.13:compile
> You expect the entire tree to have the optional flag set to true. But sadly 
> that's not the case. com.google.guava:guava and 
> com.google.code.findbugs:jsr305 are optional = false.
> I found that this is because they are managed dependencies (no difference 
> whether imported or declared directly). When I use this 
> [pom|https://github.com/evosec/export-dependencies-maven-plugin/blob/a931ee09c0880097b73e2010d71b000ede3acbfe/src/it/buck-optional-transitive-dependencies/pom.xml]
>  it works.
> There are some integration tests in this 
> [repository|https://github.com/evosec/export-dependencies-maven-plugin] that 
> demonstrate the issue. Checkout demonstrate-tree-bug branch and run "mvn 
> verify". Now compare these files in target/it
> - buck-bom-managed-optional-transitive-dependencies/target/BUCK
> - buck-managed-optional-transitive-dependencies/target/BUCK
> - buck-optional-transitive-dependencies/target/BUCK
> [The CI builds demonstrating the 
> failure|https://travis-ci.org/evosec/export-dependencies-maven-plugin/builds/81137480].
> Let me know if I can help you reproduce the problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
I will wait for [~rfscholte] or we will discuss it on mailing list.
Our problem is that a parent {{ClassLoader}}, which is {{PlatformClassLoader}}, 
of {{IsolatedClassLoader}} does not provide us with full Java stack in JDK.


> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli edited comment on SUREFIRE-1265 at 5/3/17 11:33 AM:


I'm really sorry 

Actually I have to use with Java8 to compile the whole suite
mvn clean install -Dit.test=Surefire1265Java9IT 

Than in order to start the tests I have to use this command line:
JAVA_HOME=~/dev/jdk-9 mvn verify -Dit.test=Surefire1265Java9IT

but compilation fails 
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure: 
Compilation failure:
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[2,16]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,17]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,58]
 error: package javax.xml.ws is not visible
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure

{code}





was (Author: eolivelli):
I'm really sorry 

Acutally I have to use with Java8 to compile se ruite
mvn clean install -Dit.test=Surefire1265Java9IT 

Than in order to kick the it tests in I have to use this:
JAVA_HOME=~/dev/jdk-9 mvn verify -Dit.test=Surefire1265Java9IT

but compilation fails 
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure: 
Compilation failure:
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[2,16]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,17]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,58]
 error: package javax.xml.ws is not visible
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure

{code}




> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli commented on SUREFIRE-1265:
---

I'm really sorry 

Acutally I have to use with Java8 to compile se ruite
mvn clean install -Dit.test=Surefire1265Java9IT 

Than in order to kick the it tests in I have to use this:
JAVA_HOME=~/dev/jdk-9 mvn verify -Dit.test=Surefire1265Java9IT

but compilation fails 
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure: 
Compilation failure:
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[2,16]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,17]
 error: package javax.xml.ws is not visible
[ERROR] (package javax.xml.ws is declared in module java.xml.ws, which is not 
in the module graph)
[ERROR] 
/home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/surefire-integration-tests/target/Surefire1265Java9IT_shouldRunInPluginJava9/src/test/java/J9Test.java:[18,58]
 error: package javax.xml.ws is not visible
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project surefire-1265: Compilation failure

{code}




> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
Surefire1265Java9IT  can be easily written in command line like {{mvn test}}.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana edited comment on SUREFIRE-1265 at 5/3/17 9:33 AM:


[~eolivelli]
You can use {{it.test}} property or replace **IT** with {{Surefire1265Java9IT}} 
in {{surefire-integration-tests/pom.xml}}.


was (Author: tibor17):
[~eolivelli]
You can use {{it.test}} property or replace *IT* with {{Surefire1265Java9IT}} 
in {{surefire-integration-tests/pom.xml}}.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana edited comment on SUREFIRE-1265 at 5/3/17 9:33 AM:


[~eolivelli]
You can use {{it.test}} property or replace *IT* with {{Surefire1265Java9IT}} 
in {{surefire-integration-tests/pom.xml}}.


was (Author: tibor17):
[~eolivelli]
You can use {{it.test}} property or replace {{*IT*}} with 
{{Surefire1265Java9IT}} in {{surefire-integration-tests/pom.xml}}.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
You can use {{it.test}} property or replace {{*IT*}} with 
{{Surefire1265Java9IT}} in {{surefire-integration-tests/pom.xml}}.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana edited comment on SUREFIRE-1265 at 5/3/17 9:29 AM:


[~rfscholte]
Should we put {{module-info.class}} in to the jar file or artifact which uses 
{{IsolatedClassLoader}}?
Unfortunately this would be {{surefire-booter}}.
The ideal situation would be to have it in plugin's jar only and export all 
modules in {{module-info.java}}:
module surefire.xyz {
java.activation, java.xml.bind, java.xml.ws,jdk.xml.bind
}
Should it be imported, or optional?
The whole problem is that isloated CL is used in plugin and ClassLoader does 
not have any API call to extend the PlatformClassLoader with all JDK modules. 
These modules would be nice to have as optional, means if the classes (tests) 
in CL need to load them on the fly.
What can we do about this?


was (Author: tibor17):
[~rfscholte]
Should be put {{module-info.class}} in to the jar file or artifact which uses 
{{IsolatedClassLoader}}?
Unfortunately this would be {{surefire-booter}}.
The ideal situation would be to have it in plugin's jar only and export all 
modules in {{module-info.java}}:
module surefire.xyz {
java.activation, java.xml.bind, java.xml.ws,jdk.xml.bind
}
Should it be imported, or optional?
The whole problem is that isloated CL is used in plugin and ClassLoader does 
not have any API call to extend the PlatformClassLoader with all JDK modules. 
These modules would be nice to have as optional, means if the classes (tests) 
in CL need to load them on the fly.
What can we do about this?

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~rfscholte]
Should be put {{module-info.class}} in to the jar file or artifact which uses 
{{IsolatedClassLoader}}?
Unfortunately this would be {{surefire-booter}}.
The ideal situation would be to have it in plugin's jar only and export all 
modules in {{module-info.java}}:
module surefire.xyz {
java.activation, java.xml.bind, java.xml.ws,jdk.xml.bind
}
Should it be imported, or optional?
The whole problem is that isloated CL is used in plugin and ClassLoader does 
not have any API call to extend the PlatformClassLoader with all JDK modules. 
These modules would be nice to have as optional, means if the classes (tests) 
in CL need to load them on the fly.
What can we do about this?

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


Try to copy it to another directory on your file system and run it as a regular 
project.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli commented on SUREFIRE-1265:
---

Thank you [~tibor17]
Is the test case good for you in order to see the failure ?
Otherwise I will try to add a test case to surefire-1265

IMHO This will be enough 
{code}
public class J9Test {

@Test
public void test_sql_mod() throws java.sql.SQLException {
System.out.println(System.getProperty("java.specification.version"));
}

@Test
public void test_corba_mod() /*throws org.omg.CORBA.BAD_INV_ORDER*/ {
}

@Test
public void test_javaws()  {
javax.xml.ws.Holder holder = new javax.xml.ws.Holder("test");
holder.value = "test";
}
}
{code}

is there any way to launch a single test (Surefire1265Java9IT) of the IT of 
surefire ? I am using -Dtest= but it does not work, the architecture is 
quite complex, if you give me some pointer I will come at speed to the problem


> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
This is caused by cxf plugin.
So this is not the way to go.
We have to setup JDK in JAVA_HOME for the particular IT test with JDK 9 via 
toolchain and run the IT in fork mode mean not embedded mode.
Nevertheless you must build the project with JDK 8 and run the example project 
with JDK 9.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli commented on SUREFIRE-1265:
---

Im trying to add the test case to surefire-1265 anyway

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli commented on SUREFIRE-1265:
---

I have checked out your last commit

JAVA_HOME=~/jdk-9 mvn clean install -DskipTests

the build of failsafe plugin is still  broken

{code}
[ERROR] /home/diennea.lan/enrico.olivelli/dev/eolivelli/maven-surefire/null 
[-1:-1]: Failed to create model
com.sun.istack.SAXParseException2; Failed to create model
at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:94)
at 
org.apache.cxf.maven_plugin.XSDToJavaRunner.loadModel(XSDToJavaRunner.java:233)
at 
org.apache.cxf.maven_plugin.XSDToJavaRunner.run(XSDToJavaRunner.java:169)
at 
org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.run(AbstractXSDToJavaMojo.java:336)
at 
org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJavaMojo.java:238)
at 
org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:41)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:563)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.reflect.InvocationTargetException
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:563)
at 
org.apache.cxf.maven_plugin.XSDToJavaRunner.loadModel(XSDToJavaRunner.java:229)
... 26 more
Caused by: java.lang.NoClassDefFoundError: javax/activation/DataSource
at 
com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.(RuntimeBuiltinLeafInfoImpl.java:470)
at 
com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.(RuntimeTypeInfoSetImpl.java:63)
at 
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:128)
at 
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:84)
at 
com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:162)
at 
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.(RuntimeModelBuilder.java:92)
at 
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:444)
at 
com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:292)
at 
com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:139)
at 
com.sun.xml.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(JAXBContextImpl.java:1138)
at 
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:162)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

[jira] [Commented] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Tibor Digana (JIRA)


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

Tibor Digana commented on SUREFIRE-1265:


[~eolivelli]
I committed a change yesterday. There should not be such limitation in enforcer 
anymore. Pls try again.

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SUREFIRE-1265) reuseForks=false fails on jdk-9-ea builds

2017-05-03 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli updated SUREFIRE-1265:
--
Attachment: Java9Example.zip

Attaching a a simple reproducer, Just use javax.ws.Holder in a JUnit Test case.

I tried to update the "surefire-1265" package on the integrations tests of 
surefire, but surefire itself cannot be built on Java9

run this command on the root of "maven-surefire"
{code}
JAVA_HOME=~/jdk-9 mvn clean install -DskipTests
{code}

The results is:
{code}
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
Detected JDK Version: 9 is not in the allowed range [1.6.0,1.9.0).
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce-java) on 
project surefire: Some Enforcer rules have failed. Look above for specific 
messages explaining why the rule failed. -> [Help 1]
{code}

this is my java version
{code}
java 9-ea
Java(TM) SE Runtime Environment (build 9-ea+163)
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+163, mixed mode)
{code}

> reuseForks=false fails on jdk-9-ea builds
> -
>
> Key: SUREFIRE-1265
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1265
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Musgrove
>Assignee: Tibor Digana
>  Labels: jigsaw
> Fix For: 2.20.1
>
> Attachments: j9test.tar, Java9Example.zip
>
>
> When I run any surefire test (with reuseForks=false) that uses java.sql 
> classes on recent jdk-9 ea builds it fails with:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project maven-surefire-plugin-example: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: 
> java.lang.NoClassDefFoundError: java/sql/SQLException: java.sql.SQLException 
> -> [Help 1]
> If I run it with reuseForks=true it works fine.
> This problem was introduced in jdk build 9-ea+122 
> (http://download.java.net/java/jdk9/changes/jdk-9+122.html) when the jigsaw 
> team addressed: 
> d20279be77d9  8154189 Deprivilege java.sql and java.sql.rowset module



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

52 matches

Mail list logo