[jira] [Commented] (MCOMPILER-360) NPE when calculating modulepath with invalid entries
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824984#comment-16824984 ] Rolf Schumacher commented on MCOMPILER-360: --- correct, Hendrik. I am blocked for about a year now, doing no changes to my fop tool. I am eager to get the 3.8.1 version, as the local changes I did to the git version of maven-compiler-plugin did not lead to a successful result. This may be due to that I am not used to doing changes to a maven plugin, or there are more than one problem when it comes to using modules with saxon, fop and Java >8, or the fix does not work es proposed. > NPE when calculating modulepath with invalid entries > > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Assignee: Robert Scholte >Priority: Major > Labels: build, maven, newbie > Fix For: 3.8.1 > > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz, > mvn-verify-result.txt, with-Dinvoker.txt > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:56 PM:
---
Running {{mvn}} verify {{-Prun-its}} {{-Dinvoker.test=MCOMPILER-360}} without a
toolchain.xml led to with-Dinvoker.txt, as attached.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running {{mvn}} verify {{-Prun-its}} {{-Dinvoker.test=MCOMPILER-360}} led to
with-Dinvoker.txt, as attached.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:56 PM:
---
Running {{mvn}} verify {{-Prun-its}} {{-Dinvoker.test=MCOMPILER-360}} led to
with-Dinvoker.txt, as attached.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running {{mvn}} verify {{-Prun-its}} {{-Dinvoker.test=MCOMPILER-360}} led to
with-Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:55 PM:
---
Running {{mvn}} verify {{-Prun-its}} {{-Dinvoker.test=MCOMPILER-360}} led to
with-Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running {{mvn verify --Prun-its -Dinvoker.test=MCOMPILER-360}} led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:52 PM:
---
Running {{mvn verify --Prun-its -Dinvoker.test=MCOMPILER-360}} led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running {{mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360}} led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:51 PM:
---
Running {{mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360}} led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running _{{mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360}}_ led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:51 PM:
---
Running _{{mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360}}_ led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
was (Author: ngong):
Running _mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360_ led to
with--Dinvoker.txt.
Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java
1.8.0 is installed, too, but not active. Did I get you right to run _mvn
verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use
10.0.2?
Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that
one equipped with your patch (as I guessed)? Than the np failure should have
been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn
test_. Right? Its not.
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534 ] Rolf Schumacher edited comment on MCOMPILER-360 at 9/9/18 6:50 PM: --- Running _mvn verify -Prun-its -Dinvoker.test=MCOMPILER-360_ led to with--Dinvoker.txt. Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java 1.8.0 is installed, too, but not active. Did I get you right to run _mvn verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use 10.0.2? Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that one equipped with your patch (as I guessed)? Than the np failure should have been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn test_. Right? Its not. was (Author: ngong): Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java 1.8.0 is installed, too, but not active. Did I get you right to run _mvn verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use 10.0.2? Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that one equipped with your patch (as I guessed)? Than the np failure should have been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn test_. Right? Its not. > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz, > mvn-verify-result.txt, with-Dinvoker.txt > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: with-Dinvoker.txt > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz, > mvn-verify-result.txt, with-Dinvoker.txt > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608534#comment-16608534 ] Rolf Schumacher commented on MCOMPILER-360: --- Never used a toolchain.xml. The default Java on my machine is 10.0.2, Java 1.8.0 is installed, too, but not active. Did I get you right to run _mvn verify_ with Java 1.8.0 while directing the pom.xml of MCOMPILER-360 to use 10.0.2? Also: I can _mvn install_ 3.8.1-SNAPSHOT, the one from the git repo. Is that one equipped with your patch (as I guessed)? Than the np failure should have been gone if I use 3.8.1-SNAPSHOT in pom.xml of MCOMPILER-360 an run _mvn test_. Right? Its not. > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz, > mvn-verify-result.txt > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608200#comment-16608200
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/8/18 8:46 PM:
---
Tried to, but not used to it. Attached you can find a very reduced version of
the project that still gives the failure if I do "mvn test". See
MCOMPILER-360.tar.gz. I put it under src/it it and ran the test. But it seems
that I do not reach my test as others fail before. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?
was (Author: ngong):
Tried to, but not used to it. Attached you can find a very reduced version of
the project that still yields to the failure if I do "mvn test". See
MCOMPILER-360.tar.gz. I put it under src/it it and ran the test. But it seems
that I do not reach my test as others fail before. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608200#comment-16608200
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/8/18 8:40 PM:
---
Tried to, but not used to it. Attached you can find a very reduced version of
the project that still yields to the failure if I do "mvn test". See
MCOMPILER-360.tar.gz. I put it under src/it it and ran the test. But it seems
that I do not reach my test as others fail before. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?
was (Author: ngong):
Tried to, but not used to it. Attached you can find a very reduced version of
the project that still yields to the failure if I do "mvn test". See
MCOMPILER-360.tar.gz. I put it under src/it it and ran the test. But it seems
that I do not reach my test as others fail before. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its-}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?-
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608200#comment-16608200
]
Rolf Schumacher edited comment on MCOMPILER-360 at 9/8/18 8:39 PM:
---
Tried to, but not used to it. Attached you can find a very reduced version of
the project that still yields to the failure if I do "mvn test". See
MCOMPILER-360.tar.gz. I put it under src/it it and ran the test. But it seems
that I do not reach my test as others fail before. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its-}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?-
was (Author: ngong):
Tried to, but not used to it. Attached a very reduced version of the project
that still yields to the failure if I do "mvn test". See MCOMPILER-360.tar.gz.
However under src/it it seems that I do not reach my test as others fail before
it reaches it. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?--
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MCOMPILER-360) nullpointer exception
[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608200#comment-16608200
]
Rolf Schumacher commented on MCOMPILER-360:
---
Tried to, but not used to it. Attached a very reduced version of the project
that still yields to the failure if I do "mvn test". See MCOMPILER-360.tar.gz.
However under src/it it seems that I do not reach my test as others fail before
it reaches it. See mvn-verify-result.txt.
Also {{mvn verify -Prun-its}} takes very long. How to concentrate on this
issue? Deleting others from src/it? What not to delete?--
> nullpointer exception
> -
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
>Reporter: Rolf Schumacher
>Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: mvn-verify-result.txt > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz, > mvn-verify-result.txt > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: MCOMPILER-360.tar.gz > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: (was: pom.xml) > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: (was: xslt.zip) > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, pom.xml > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608073#comment-16608073 ] Rolf Schumacher commented on MCOMPILER-360: --- Ok, I get the same failure with the attached reduced pom.xml. Sorry, what is "src/it"? > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, pom.xml, xslt.zip > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: pom.xml > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, pom.xml, xslt.zip > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607504#comment-16607504 ] Rolf Schumacher commented on MCOMPILER-360: --- I can attach the project that caused the exception. It's absolutely free - at least on my part. It's just a wrapper around Saxon that I've written years ago, adapted to newer needs from time to time. I've loaded it to Eclipse Proton with m2e. But it works in the same way if you just run "mvn test" from the command line. I've set the JDK_JAVA_OPTIONS: --add-modules=java.se.ee. In case this does not work for you (or even if it does), please provide me instruction on how I can use your improved maven-compiler-plugin. I will report the result. > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, xslt.zip > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-360) nullpointer exception
[ https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rolf Schumacher updated MCOMPILER-360: -- Attachment: xslt.zip > nullpointer exception > - > > Key: MCOMPILER-360 > URL: https://issues.apache.org/jira/browse/MCOMPILER-360 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 > Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 > (2018-08-21) x86_64 GNU/Linux > java version "10.0.2" 2018-07-17 > Apache Maven 3.5.4 >Reporter: Rolf Schumacher >Priority: Major > Labels: build, maven, newbie > Attachments: 2018-09-06-stacktrace.txt, xslt.zip > > > Trying to migrate an saxon/fop maven project to Java 10. > Added module-info.java, entered all required Automatic names. No compiler > failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a > maven-compile-plugin error > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project xslt: Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. > NullPointerException -> [Help 1] > Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCOMPILER-360) nullpointer exception
Rolf Schumacher created MCOMPILER-360: - Summary: nullpointer exception Key: MCOMPILER-360 URL: https://issues.apache.org/jira/browse/MCOMPILER-360 Project: Maven Compiler Plugin Issue Type: Bug Affects Versions: 3.8.0 Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux java version "10.0.2" 2018-07-17 Apache Maven 3.5.4 Reporter: Rolf Schumacher Attachments: 2018-09-06-stacktrace.txt Trying to migrate an saxon/fop maven project to Java 10. Added module-info.java, entered all required Automatic names. No compiler failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a maven-compile-plugin error Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project xslt: Execution default-compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed. NullPointerException -> [Help 1] Full output is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] Closed: (MJAR-141) manifestEntry seems not to work correctly
[
http://jira.codehaus.org/browse/MJAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rolf Schumacher closed MJAR-141.
Resolution: Fixed
This was not a bug.
> manifestEntry seems not to work correctly
> -
>
> Key: MJAR-141
> URL: http://jira.codehaus.org/browse/MJAR-141
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
> Environment: linux 32 bit, Eclipse 3.5
>Reporter: Rolf Schumacher
>Priority: Blocker
> Attachments: pom.xml
>
>
> using in pom.xml the maven-jar-plugin ...
> {{xxyy}}
> breaks the generation of MANIFEST.MF while
> {{value}} works as expected.
> attached you find the complete pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-141) manifestEntry seems not to work correctly
[
http://jira.codehaus.org/browse/MJAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253245#action_253245
]
Rolf Schumacher commented on MJAR-141:
--
ok, found a solution:
do not use the key=name, instead use a concept called "section" (for what ever):
rewriting the code did the trick:
{code:xml}
font/BOMBLOGO.TTF
application/x-font
{code}
> manifestEntry seems not to work correctly
> -
>
> Key: MJAR-141
> URL: http://jira.codehaus.org/browse/MJAR-141
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
> Environment: linux 32 bit, Eclipse 3.5
>Reporter: Rolf Schumacher
>Priority: Blocker
> Attachments: pom.xml
>
>
> using in pom.xml the maven-jar-plugin ...
> {{xxyy}}
> breaks the generation of MANIFEST.MF while
> {{value}} works as expected.
> attached you find the complete pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAR-141) manifestEntry seems not to work correctly
manifestEntry seems not to work correctly
-
Key: MJAR-141
URL: http://jira.codehaus.org/browse/MJAR-141
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Environment: linux 32 bit, Eclipse 3.5
Reporter: Rolf Schumacher
Priority: Blocker
Attachments: pom.xml
using in pom.xml the maven-jar-plugin ...
{{xxyy}}
breaks the generation of MANIFEST.MF while
{{value}} works as expected.
attached you find the complete pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-182) manifestEntry seems not to work correctly
[ http://jira.codehaus.org/browse/MSHARED-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253070#action_253070 ] Rolf Schumacher commented on MSHARED-182: - sorry, all indentation is gone and I can not correct it. > manifestEntry seems not to work correctly > - > > Key: MSHARED-182 > URL: http://jira.codehaus.org/browse/MSHARED-182 > Project: Maven Shared Components > Issue Type: Bug > Environment: maven-jar-plugin 2.3.1 >Reporter: Rolf Schumacher >Priority: Blocker > > hope this is the correct place ot file an issue about maven-jar-plugin > > org.apache.maven.plugins > maven-jar-plugin > 2.3.1 > > > > > true > > eu.ngong.xslt.App > > /usr/share/java/ > > > xxx > > yyy > > > > > does not work: silently neither a classpass is generated nor the requested > entries Name and Content-Type. > If I exchange the manifestEntries by > > value > > it works: the classpath is generated in MANIFEST.MF as well as the "key: > value" line. > If I exchange the manifestEntries by > > value > > it does not work: the classpath is generated but not the "Key: value" line. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHARED-182) manifestEntry seems not to work correctly
manifestEntry seems not to work correctly - Key: MSHARED-182 URL: http://jira.codehaus.org/browse/MSHARED-182 Project: Maven Shared Components Issue Type: Bug Environment: maven-jar-plugin 2.3.1 Reporter: Rolf Schumacher Priority: Blocker hope this is the correct place ot file an issue about maven-jar-plugin org.apache.maven.plugins maven-jar-plugin 2.3.1 true eu.ngong.xslt.App /usr/share/java/ xxx yyy does not work: silently neither a classpass is generated nor the requested entries Name and Content-Type. If I exchange the manifestEntries by value it works: the classpath is generated in MANIFEST.MF as well as the "key: value" line. If I exchange the manifestEntries by value it does not work: the classpath is generated but not the "Key: value" line. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
