[sysdeo-tomcat] System scoped dependencies not handled properly in .tomcatplugin
--------------------------------------------------------------------------------
Key: MOJO-992
URL: http://jira.codehaus.org/browse/MOJO-992
Project: Mojo
Issue Type: Bug
Components: sysdeo-tomcat
Reporter: Tim O'Brien
Priority: Critical
I've got a project which uses a system scoped dependency with a systemPath of
${basedir}/lib/jvyaml-0.2.1.jar. This is used when a dependency does not have
a publically available artifact in a Maven repository. When I run "mvn
eclipse:eclipse sysdeo-tomcat:generate" I get a .tomcatplugin with the
following entry:
<webClassPathEntry>M2_REPO/org/jvyaml/jvyaml/0.2.1/jvyaml-0.2.1.jar</webClassPathEntry>
This isn't the right answer. :-( It should be resolving the dependency and
putting the absolute path in the .tomcatplugin file.
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
