[NPANDAY-622] NPE - compile:testCompile

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0-incubating
• Fix Version/s: 1.5.0-incubating
• Component/s: Maven Plugins

Environment

VS 2013

• Assignee: Brett Porter
• Reporter: Greg Domjan
• Created: 20/May/14 04:24
• Updated: 10/Jul/14 06:08
• Resolved: 09/Jul/14 07:30

Description

As compile:compile cannot be skipped, needed to use custom-lifecycle-maven-plugin as the lifecycle extension to use tlbimp in createing the library.
<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>custom-lifecycle-maven-plugin</artifactId>
<extensions>true</extensions>
</plugin>

Following that, to add a test process tying to add

<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>maven-compile-plugin</artifactId>
<configuration>
<frameworkVersion>3.0</frameworkVersion>
</configuration>
<executions>
<execution>
<id>testing</id>
<goals>
<goal>process-test-sources</goal>
<goal>testCompile</goal>
</goals>
<configuration>
</configuration>
</execution>
</executions>
</plugin>

[INFO] [compile:testCompile

{execution: testing}

]
[INFO] NPANDAY-148-009: Took 11ms to resolve dependencies for group:art:library:8.1.0-0-SNAPSHOT with filter org
.apache.maven.artifact.resolver.filter.AndArtifactFilter@4f14e777
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at npanday.assembler.impl.AssemblerContextImpl.getClassExtensionFor(AssemblerContextImpl.java:190)
at npanday.plugin.compile.AbstractCompilerMojo.getLanguageFileExtension(AbstractCompilerMojo.java:1471)
at npanday.plugin.compile.TestCompilerMojo.getCompilerConfig(TestCompilerMojo.java:104)
at npanday.plugin.compile.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1186)
at npanday.plugin.compile.TestCompilerMojo.execute(TestCompilerMojo.java:59)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------

It appears there is some dependency in testCompile that requires running the goal within the Compile as extension?