[jira] [Updated] (MDEP-952) Unpack fails if extension of artifact is used

2024-08-21 Thread Pascal Schumacher (Jira) 


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

Pascal Schumacher updated MDEP-952:
---
Description: 
With 3.6.0 this works:


{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2 
kB/s)
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO] 
{quote}


but it fails with 3.7.0 and 3.7.1:

{quote}

mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on 
project standalone-pom: Execution default-cli of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.: 
NullPointerException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{quote}

If the extension is omitted it works with all version (This is a simplified 
example, the real use case is a private zip artifact.)

I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.

By the way: Thank you very much for developing/providing the Maven Dependency 
Plugin.

  was:
With 3.6.0 this works:


{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on 
project standalone-pom: Execution default-cli of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.: 
NullPointerException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{quote}


but it fails with 3.7.0 and 3.7.1:

{quote}

org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.

[jira] [Updated] (MDEP-952) Unpack fails if extension of artifact is used

2024-08-21 Thread Pascal Schumacher (Jira) 


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

Pascal Schumacher updated MDEP-952:
---
Description: 
With 3.6.0 this works:


{quote}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
[INFO] Finished at: 2024-08-21T17:00:12+02:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack (default-cli) on 
project standalone-pom: Execution default-cli of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack failed.: 
NullPointerException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{quote}


but it fails with 3.7.0 and 3.7.1:

{quote}

org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
{quote}

If the extension is omitted it works with all version (This is a simplified 
example, the real use case is a private zip artifact.)

I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.

By the way: Thank you very much for developing/providing the Maven Dependency 
Plugin.

  was:
With 3.6.0 this works:


{quote}

mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2 
kB/s)
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO] 

{quote}


but it fails with 3.7.0 and 3.7.1:

{quote}

org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
{quote}

If the extension is omitted it works with all version (This is a simplified 
example, the real use case is a private zip artifact.)

I tried it with Maven

[jira] [Created] (MDEP-952) Unpack fails if extension of artifact is used

2024-08-21 Thread Pascal Schumacher (Jira) 
Pascal Schumacher created MDEP-952:
--

 Summary: Unpack fails if extension of artifact is used
 Key: MDEP-952
 URL: https://issues.apache.org/jira/browse/MDEP-952
 Project: Maven Dependency Plugin
  Issue Type: Bug
  Components: unpack
Affects Versions: 3.7.1, 3.7.0
Reporter: Pascal Schumacher


With 3.6.0 this works:


{quote}

mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirectory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.6.0:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:LATEST:jar
Downloading from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml
Downloaded from artifactory-dms-maven-virtual: 
https://REPO/org/apache/commons/commons-lang3/maven-metadata.xml (1.8 kB at 4.2 
kB/s)
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  2.231 s
[INFO] Finished at: 2024-08-21T16:59:57+02:00
[INFO] 

{quote}


but it fails with 3.7.0 and 3.7.1:

{quote}

org.apache.maven.plugins:maven-dependency-plugin:3.7.1:unpack 
-Dartifact=org.apache.commons:commons-lang3:LATEST::jar -DoutputDirec
tory=.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- dependency:3.7.1:unpack (default-cli) @ standalone-pom ---
[INFO] Configured Artifact: org.apache.commons:commons-lang3:jar:LATEST:null
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.859 s
{quote}

If the extension is omitted it works with all version (This is a simplified 
example, the real use case is a private zip artifact.)

I tried it with Maven 3.9.5 and 3.9.9 on both Linux and Windows.

By the way: Thank you very much for developing/providing the Maven Dependency 
Plugin.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MJAVADOC-509) additionalParam are overridden when used in maven release plugin ?

2018-01-07 Thread Pascal Schumacher (JIRA) 

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

Pascal Schumacher commented on MJAVADOC-509:


[~jocosti] I could replicated this error with maven javadoc plugin version 
3.0.0 and jdk 1.8.0_152 and 9.0.1. "mvn javadoc:javadoc" of the AssertJ failed 
every time.

I was able to solve this be replacing "additinonalParam" with 
"additionalOptions".

It looks like "additionalParam" was removed in version 3.0.0.

I guess this defect can be closed.



> additionalParam are overridden when used in maven release plugin ?
> --
>
> Key: MJAVADOC-509
> URL: https://issues.apache.org/jira/browse/MJAVADOC-509
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0-M1
> Environment: Linux ubuntu 16.04
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
> 2017-10-18T20:58:13+13:00)
> Maven home: /home/joel/prog/apache-maven-3.5.2
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /home/joel/prog/java/jdk1.8.0_144/jre
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-104-generic", arch: "amd64", family: "unix"
>Reporter: Joel Costigliola
>
> I believe https://issues.apache.org/jira/browse/MJAVADOC-387 introduced a 
> regression as it overrides any value set in {{additionalparam}} which only 
> manifests when using the maven release plugin 
> My open source project 
> ([AssertJ|http://joel-costigliola.github.io/assertj/index.html]) adds 
> javascript to the javadoc footer I thus need to add this parameter to be able 
> to generate the javadoc:
> {{--allow-script-in-comments}}
> The {{mvn release:perform}} command failed with this error:
> {noformat}
> [INFO] Exit code: 1 - javadoc: error - Argument for -footer contains 
> JavaScript.
> [INFO] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> the debug log shows that the {{--allow-script-in-comments}} parameter I set 
> was not honored:
> {noformat}
> [INFO] [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:jar' with basic 
> configurator -->
> [INFO] [DEBUG]   (f) additionalparam = -Xdoclint:none
> {noformat}



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

[jira] [Commented] (MSITE-796) Unable to generate site with JDK9 - java.lang.ExceptionInInitializerError / Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1

2017-10-13 Thread Pascal Schumacher (JIRA) 

[ 
https://issues.apache.org/jira/browse/MSITE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203717#comment-16203717
 ] 

Pascal Schumacher commented on MSITE-796:
-

Great to see that this is fixed. A release with this fix would be great. Thanks!

> Unable to generate site with JDK9 - java.lang.ExceptionInInitializerError / 
> Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1
> --
>
> Key: MSITE-796
> URL: https://issues.apache.org/jira/browse/MSITE-796
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.6
> Environment: maven site plugin 3.6 running with JDK9 on
> https://github.com/ottlinger/fotorenamer - Branch: master
> https://github.com/ottlinger/fotorenamer/blob/master/pom.xml
>Reporter: Philipp Ottlinger
>Assignee: Robert Scholte
> Fix For: 3.7
>
>
> My project worked with JDK8, after switching to JDK9 and updating a load of 
> dependencies I run into the following stacktrace while executing:
> {code}
> $ mvn site:site
> $ Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T21:39:06+02:00)
> Maven home: /home/mesoftware/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /home/me/jdk-9
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-96-generic", arch: "amd64", family: "unix"
> {code}
> Not sure if it's related to the version parsing 
> {code}
> [DEBUG] Processing Velocity for template META-INF/maven/site.vm on 
> rat-report.html
> [DEBUG] Velocimacro : added VM topMenu: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM topLink: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM topLinks: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM link: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM image: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM banner: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM links: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM breadcrumbs: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM displayTree: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM menuItem: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM mainMenu: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM copyright: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM publishDate: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM builtByLogo: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM piwik: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM googleAnalytics: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM googleSearch: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM forkMeOnGitHub: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM prjProfile: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM googlePlusOne: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM facebookLike: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM followTwitter: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM ohloh: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM flattrHead: source=META-INF/maven/site.vm
> [DEBUG] Velocimacro : added VM flattrBody: source=META-INF/maven/site.vm
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 22.171 s
> [INFO] Finished at: 2017-09-26T23:19:47+02:00
> [INFO] Final Memory: 66M/220M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project 
> fotorenamer: Execution default-cli of goal 
> org.apache.maven.plugins:maven-site-plugin:3.6:site failed: An API 
> incompatibility was encountered while executing 
> org.apache.maven.plugins:maven-site-plugin:3.6:site: 
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.6
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/home/me/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.6/maven-site-plugin-3.6.jar
> [ERROR] urls[1] = 
> file:/home/me/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.3/maven-reporting-exec-1.3.jar
> [ERROR] urls[2] = 
> file:/home/me/.m2/repository/org/apache/mave

[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

2017-04-26 Thread Pascal Schumacher (JIRA) 

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

Pascal Schumacher commented on MNG-6112:


It would be very nice if this was released in 3.5.1.

> Central repository in the 4.0.0 super POM should declare update policy 
> 'never'.
> ---
>
> Key: MNG-6112
> URL: https://issues.apache.org/jira/browse/MNG-6112
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.0-beta-1
>Reporter: Christian Schulte
> Fix For: 3.5.1-candidate
>
>




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

[jira] [Created] (MCOMPILER-291) No possible use compilerArgs arg "-J--add-opens" multiple times

2017-03-24 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created MCOMPILER-291:
---

 Summary: No possible use compilerArgs arg "-J--add-opens" multiple 
times
 Key: MCOMPILER-291
 URL: https://issues.apache.org/jira/browse/MCOMPILER-291
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.6.1
Reporter: Pascal Schumacher


I'm trying to a project with uses lombok to work with java 9.

{code}

org.apache.maven.plugins
maven-compiler-plugin
3.6.1

1.8
1.8
true


-J--add-opens-Jjdk.compiler/com.sun.tools.javac.processing=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.model=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED

-J--add-opens-Jjdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED



{code}

{code}mvn -X compile{code} shows me that the {code}-J--add-opens{code} 
arguments are collapsed:

{code}
cmd.exe /X /C ""C:\Program Files\Java\jdk-9\bin\javac.exe" 
@C:/Users/User/random-beans/random-beans/target/classes/org.codehaus.plexus.compiler.javac.JavacCompiler9403484282707867963arguments
 -J--add-opens -Jjdk.compiler/com.sun.tools.javac.processing=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.model=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED 
-Jjdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED"
{code}

which results in:

{code}Error: Main Class jdk.compiler.com.sun.tools.javac.util=ALL-UNNAMED could 
not be found or load{code}



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

[jira] [Created] (MSITE-789) Failure on java 9(-ea+159): Unable to make private java.io.File(java.lang.String,java.io.File) accessible

2017-03-04 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created MSITE-789:
---

 Summary: Failure on java 9(-ea+159): Unable to make private 
java.io.File(java.lang.String,java.io.File) accessible
 Key: MSITE-789
 URL: https://issues.apache.org/jira/browse/MSITE-789
 Project: Maven Site Plugin
  Issue Type: Bug
Affects Versions: 3.6
 Environment: java 9-ea+159
Reporter: Pascal Schumacher


{{mvn -X clean site}} of commons-texts (and I guess of every other project) 
fails with the following error trace:

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project 
commons-text: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to make 
private java.io.File(java.lang.String,java.io.File) accessible: module 
java.base does not "opens java.io" to unnamed module @47313e46 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project 
commons-text: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to make 
private java.io.File(java.lang.String,java.io.File) accessible: module 
java.base does not "opens java.io" to unnamed module @47313e46
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:547)
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: org.apache.maven.plugin.PluginExecutionException: Execution 
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.6:site 
failed: Unable to make private java.io.File(java.lang.String,java.io.File) 
accessible: module java.base does not "opens java.io" to unnamed module 
@47313e46
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make 
private java.io.File(java.lang.String,java.io.File) accessible: module 
java.base does not "opens java.io" to unnamed module @47313e46
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:335)
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:278)
at 
java.base/java.lang.reflect.Constructor.checkCanSetAccessible(Constructor.java:191)
at 
java.base/java.lang.reflect.Constructor.setAccessible(Constructor.java:184)
at 
org.codehaus.groovy.reflection.CachedConstructor.(CachedConstructor.java:32)
at 
org.codehaus.groovy.reflection.CachedClass.getConstructors(CachedClass.java:233)
at groovy.lang.MetaClassImpl.(MetaClassImpl.java:115)
at 
groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createNormalMetaClass(MetaClassRegistry.java:102)
at 
groovy.lang.MetaClassRegistry$MetaClassCreationHandle.create(MetaClassRegistry.java:92)
at 
org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getGlobalMetaClass(Meta

[jira] [Created] (MCHANGES-375) Add stop between issue text and " Fixes issue-number"

2016-10-02 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created MCHANGES-375:
--

 Summary: Add stop between issue text and " Fixes issue-number"
 Key: MCHANGES-375
 URL: https://issues.apache.org/jira/browse/MCHANGES-375
 Project: Maven Changes Plugin
  Issue Type: Improvement
Affects Versions: 2.12
Reporter: Pascal Schumacher
Priority: Minor


The change-report would be easier to read if there was a stop between the issue 
text and the "Fixes issue-number" part. 

E.g the current commons-lang release candidate report contains entries like 
this:

{quote}Added a new property IS_OS_MAC_OSX_EL_CAPITAN in SystemUtils Fixes 
LANG-1273. Thanks to Jake Wang.{quote}

My suggestion is to change it to

{quote}Added a new property IS_OS_MAC_OSX_EL_CAPITAN in SystemUtils. Fixes 
LANG-1273. Thanks to Jake Wang.{quote}

source: 
[http://home.apache.org/~britter/commons/lang/3_5_RC1/changes-report.html#a3.4]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] (SUREFIRE-1065) Allow includesFile and excludesFile parameters to be set from the commandline

2015-01-02 Thread Pascal Schumacher (JIRA) 

[ 
https://jira.codehaus.org/browse/SUREFIRE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360542#comment-360542
 ] 

Pascal Schumacher commented on SUREFIRE-1065:
-

Thank you very much for adding this. :)

> Allow includesFile and excludesFile parameters to be set from the commandline
> -
>
> Key: SUREFIRE-1065
> URL: https://jira.codehaus.org/browse/SUREFIRE-1065
> Project: Maven Surefire
>  Issue Type: Improvement
>Reporter: Pascal Schumacher
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 2.19
>
>
> It would be nice to be able to set the includesFile and excludesFile 
> parameters from the command line.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1065) Allow includesFile and excludesFile parameters to be set from the commandline

2014-02-21 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created SUREFIRE-1065:
---

 Summary: Allow includesFile and excludesFile parameters to be set 
from the commandline
 Key: SUREFIRE-1065
 URL: https://jira.codehaus.org/browse/SUREFIRE-1065
 Project: Maven Surefire
  Issue Type: Improvement
Reporter: Pascal Schumacher
Priority: Minor


It would be nice to be able to set the includesFile and excludesFile parameters 
from the command line.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1064) Provide a way to run only failed tests

2014-02-20 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created SUREFIRE-1064:
---

 Summary: Provide a way to run only failed tests
 Key: SUREFIRE-1064
 URL: https://jira.codehaus.org/browse/SUREFIRE-1064
 Project: Maven Surefire
  Issue Type: New Feature
  Components: Maven Failsafe Plugin
Reporter: Pascal Schumacher


We use maven for end-to-end tests of a highly asynchronous system (which 
includes third-party software we can not modify). Sometimes only 1-3 out of 
hundreds of test fail. It would be nice if there were a way to rerun these 
failed test only.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)