Mojo Sysdeo Tomcat Plugin

[sysdeo-tomcat] System scoped dependencies not handled properly in .tomcatplugin

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

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.

Activity

Hide
Permalink
Tim O'Brien added a comment -

Michael Podrazik just sent both a bug report and a patch to fix this issue. Evidently, I wasn't handling system scoped dependencies here, so that if you were using a system scoped dependency the plugin would produce bogus classpath entries.

Thanks.

Show
Tim O'Brien added a comment - Michael Podrazik just sent both a bug report and a patch to fix this issue. Evidently, I wasn't handling system scoped dependencies here, so that if you were using a system scoped dependency the plugin would produce bogus classpath entries. Thanks.

People

  • Assignee:
    Unassigned
    Reporter:
    Tim O'Brien
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: