[
https://issues.apache.org/jira/browse/MTOMCAT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-134.
------------------------------------------
Resolution: Fixed
patch applied.
Thanks!
> Empty additionalClasspathDir causes NPE in RunMojo.java
> -------------------------------------------------------
>
> Key: MTOMCAT-134
> URL: https://issues.apache.org/jira/browse/MTOMCAT-134
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6, tomcat7
> Affects Versions: 2.0-beta-1
> Environment: <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>
> Reporter: John Meyer
> Assignee: Olivier Lamy (*$^¨%`£)
> Priority: Minor
> Fix For: 2.0
>
> Attachments: MTOMCAT-134.diff
>
>
> Hit an issue where specifying an empty additionalClasspathDir caused a
> mysterious NPE and no explaination of what was wrong
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
