[
http://jira.codehaus.org/browse/MOJO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MOJO-996:
------------------------------------
Assignee: nicolas de loof
done
> Synchronize Dependency Resolution Code with Latest Eclipse Plugin
> -----------------------------------------------------------------
>
> Key: MOJO-996
> URL: http://jira.codehaus.org/browse/MOJO-996
> Project: Mojo
> Issue Type: Bug
> Components: sysdeo-tomcat
> Reporter: Tim O'Brien
> Assignee: nicolas de loof
>
> Big annoying problem uncovered wrt to system scoped dependencies. If
> .classpath contains, a classpath entry like:
> C:/blah/foo.jar
> and, .tomcatplugin contains a classpath entry:
> c:/blah/foo.jar
> The dependency is not included in the DevLoader classpath. Clearly, Sysdeo
> Tomcat eclipse plugin is doing some behind the scenes reconciliation to
> figure out what should be checked on the DevLoader preferences and what
> shouldn't be checked.
> I put in a screwy hackish fix to get this working on Windows, where I'm just
> upcasing the first character in an absolute path. The real fix would be
> to make sure the dependency resolution is sync'd with the dependency
> resolution used in the most recent Eclipse plugin. There was some recent
> discussion of separating the dependency resolution stuff out to a seaprate
> project. We should look at that before doing anything else.
--
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
