> But if I must do manual dependency analysis every time I update a third > party jar -- just in case it now incurs a new dependency for me -- then what > value are transitive dependencies in Maven at all?
You are expected to know what Jars your project (specifically) depends on. I've followed this thread and still don't understand why you don't know this. If artifacts you depend on have dependencies themselves (which is what should happen when one class extends another), they should be declared in the pom files of those projects. If those artifacts do not properly declare the scope of all of their dependencies, such that a needed class is not being found during compilation/testing/runtime, then you need to talk to the owner of the "bad" artifact. If those artifacts do not have pom files at all (you're using mvn install:install-file or deploy:deploy-file on them), then that is another issue. Maven's (transitive) dependency management works extremely well for a lot of people. I still don't know why you're having such troubles with it, and I can only blame the artifacts you're working with and not the system itself at this point. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
