[jira] [Created] (MNGSITE-313) Add documentation for MNG-1493 (referencing POM file in )
Till Brychcy created MNGSITE-313: Summary: Add documentation for MNG-1493 (referencing POM file in ) Key: MNGSITE-313 URL: https://issues.apache.org/jira/browse/MNGSITE-313 Project: Maven Project Web Site Issue Type: Improvement Reporter: Till Brychcy I yesterday learned about the feature implemented in https://issues.apache.org/jira/browse/MNG-1493 and noted it is not documented in the POM reference https://maven.apache.org/pom.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNGSITE-313) Add documentation for MNG-1493 (referencing POM file in )
[ https://issues.apache.org/jira/browse/MNGSITE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Brychcy updated MNGSITE-313: - Attachment: MNGSITE-313-maven-site.patch > Add documentation for MNG-1493 (referencing POM file in ) > - > > Key: MNGSITE-313 > URL: https://issues.apache.org/jira/browse/MNGSITE-313 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Till Brychcy > Attachments: MNGSITE-313-maven-site.patch > > > I yesterday learned about the feature implemented in > https://issues.apache.org/jira/browse/MNG-1493 > and noted it is not documented in the POM reference > https://maven.apache.org/pom.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNGSITE-313) Add documentation for MNG-1493 (referencing POM file in )
[ https://issues.apache.org/jira/browse/MNGSITE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110685#comment-16110685 ] Till Brychcy commented on MNGSITE-313: -- ping! can anybody please merge this documentation patch? > Add documentation for MNG-1493 (referencing POM file in ) > - > > Key: MNGSITE-313 > URL: https://issues.apache.org/jira/browse/MNGSITE-313 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Till Brychcy > Attachments: MNGSITE-313-maven-site.patch > > > I yesterday learned about the feature implemented in > https://issues.apache.org/jira/browse/MNG-1493 > and noted it is not documented in the POM reference > https://maven.apache.org/pom.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MCOMPILER-355) NPE in CompilerMojo.preparePaths on exception
[
https://issues.apache.org/jira/browse/MCOMPILER-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639407#comment-16639407
]
Till Brychcy commented on MCOMPILER-355:
The NPE is a duplicate of MCOMPILER-360. The root of the problem is
MCOMPILER-359
> NPE in CompilerMojo.preparePaths on exception
> -
>
> Key: MCOMPILER-355
> URL: https://issues.apache.org/jira/browse/MCOMPILER-355
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Environment: ubunutu 18.04.
>Reporter: Brett Sutton
>Priority: Major
> Attachments: testpom.zip
>
>
> I'm getting:
>
> {code:java}
>
> Caused by: java.lang.NullPointerException
> at org.apache.maven.plugin.compiler.CompilerMojo.preparePaths
> (CompilerMojo.java:244)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
> (AbstractCompilerMojo.java:787)
> at org.apache.maven.plugin.compiler.CompilerMojo.execute
> (CompilerMojo.java:188)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> {code}
>
> Appears to be caused by the exception handling assuming the 'cause' will be
> non-null:
> line 244 is:
> {code:java}
> 243 Throwable cause = pathException.getValue().getCause();
> 244 while ( cause.getCause() != null )
> 245 {
> 246 cause = cause.getCause();
> 247 }{code}
>
> Clearly in some cases pathException.getValue().getCause() is returning null.
> This occurs when I try to build a java 10 project using:
> {code:java}
> mvn deploy{code}
>
> I've narrowed the problem down to this dependancy:
> {code:java}
>
> org.javamoney
> moneta
> 1.3
> pom
> {code}
> If you remove the above dependency then the problem goes away.
> So there is likely to be two problems here. The initial NPE which should be
> easy to fix and then possibly the root cause of the exception.
> Full pom is:
> {code:java}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> au.com.noojee
> noojeebilling.api
> 1.4-SNAPSHOT
>
>
>
> src/main/java
>
>
> maven-compiler-plugin
> 3.8.0
>
> 10
>
>
>
>
>
> io.packagecloud.maven.wagon
> maven-packagecloud-wagon
> 0.0.6
>
>
>
>
>
> noojee-internal
> packagecloud+https://packagecloud.io/noojee/internal
>
>
> noojee-internal
> packagecloud+https://packagecloud.io/noojee/internal
>
>
>
>
>
>
> com.google.code.gson
> gson
> 2.8.5
>
>
>
> org.apache.logging.log4j
> log4j-core
> 2.9.1
>
>
>
> org.javamoney
> moneta
> 1.3
> pom
>
>
>
> org.bouncycastle
> bcprov-jdk15on
> 1.59
>
>
> junit
> junit
> 4.11
> test
>
>
>
>
> {code}
>
>
>
>
>
>
--
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=16639432#comment-16639432 ] Till Brychcy commented on MCOMPILER-360: I've verified that the added test fails without the fix and succeeds with 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, 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)
