I am using the eclipse plugin for a project in which project.xml lists a dependency on a <type>tld</type> artifact. maven eclipse then generates a dependency on MAVEN_REPO/path/file.tld Arguable this has no value, but Eclipse also does not like it, producing "Unbound classpath variable" messages. Manually removing these guys in Eclipse solves the problem, but of course each execute of maven eclipse reintroduces the problem.
It seems that one can add a <eclipse.depency> property to each dependency to cause special behavior. I think a solution would be to either: - Introduce a new property <eclipse.exclude>, or - Make the eclipse plug-in aware of the supported artifact types and only include artifacts of type: jar, war, sar etc. but not tld
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
