dependency-resolution: eclipse-plugin vs. webstart-plugin

[Tobias Vogel <to...@zieltraffic.de>]

Hi all,

I got a strange problem with the maven-webstart-plugin, it loses sight
of some dependencies needed for the project. For example, the jakarta
commons-codec lib is needed (derived dependency from a directly included
artifact), but won't be included when generating the webstart-files.

The strange thing is: The eclipse-plugin catches this dependency and
correctly adds it to the project's classpath. Do these two plugins have
different strategies for discovering dependencies? Does anyone have
suggestions on how to resolve this issue?

Kind regards,
Tobias Vogel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org