This shows that at least one more entry should be in the dependency element: the java package(s) !
A kind of related idea: we could even have a maven classloader that would have grasp at all java packages provided by downloadable projects (is this actually a part of the project.xml ?) which would then choose something like the latest distribution version (or...) for each package for which a class is asked to be loaded.
That would solve a fair amount of classpath definition problems which is currently a severe limitation, I think. That tool should, of course, be able to generate a dependency list from, say, running a program...
Paul
Le Dimanche, 26 janv 2003, � 20:58 Europe/Berlin, Christian Russ a �crit :
[ERROR] Caused by: java.lang.NoClassDefFoundError: de/hunsicker/io/FileFormat
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
