Enhancement: Support Java EE descriptor dependencies #4
Description
It seems that epdv checks only the .project/.classpath files. But Java EE
projects have their dependencies codified primarily through MANIFEST.MF
files, and for WTP projects, other files like
.settings/org.eclipse.wst.common.component. In my projects, I don't even
create the standard dependencies (Java Build Path), only the Java EE Module
Dependencies, because Eclipse handles the latter and manages to compile,
debug, deploy etc. without the standard dependencies.
If you implement this, a nice tough would be an option to consider ONLY the
Java EE dependencies, ignoring the standard ones completely. This would
produce a dependency graph that's closer to the deployment structure (i.e.,
which jars are included in which EARs) and not to the compilation. The
deployment structure is much "flatter" than compilation, but not completely
flat (we can have jars inside a WAR, and WARs inside EARs).
Original issue reported on code.google.com by [email protected] on 8 Oct 2008 at 8:04