Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.0-beta-1
-
None
-
<plugin>
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat7-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<configuration>
<port>9090</port>
<path>/myapp-1.0</path>
<!--contextFile></contextFile-->
<systemProperties></systemProperties>
<useTestClasspath>false</useTestClasspath>
<additionalClasspathDirs>
<additionalClasspathDir></additionalClasspathDir>
</additionalClasspathDirs>
</configuration>
<executions>
<execution>
<id>tomcat-run</id>
<goals>
<goal>exec-war-only</goal>
</goals>
<phase>package</phase>
<configuration>
<path>/myapp-1.0</path>
</configuration>
</execution>
</executions>
</plugin><plugin> <groupId>org.apache.tomcat.maven</groupId> <artifactId>tomcat7-maven-plugin</artifactId> <version>2.0-SNAPSHOT</version> <configuration> <port>9090</port> <path>/myapp-1.0</path> <!--contextFile></contextFile--> <systemProperties></systemProperties> <useTestClasspath>false</useTestClasspath> <additionalClasspathDirs> <additionalClasspathDir></additionalClasspathDir> </additionalClasspathDirs> </configuration> <executions> <execution> <id>tomcat-run</id> <goals> <goal>exec-war-only</goal> </goals> <phase>package</phase> <configuration> <path>/myapp-1.0</path> </configuration> </execution> </executions> </plugin>
Description
Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong