Hi,
I have a project in which a module, say "A", has a runtime dependency (not
required during compile) to another module ("B").
Without explicitly adding the dependency to A's POM file it compiles
(everything is passed to A as "object"). But during runtime it won't find "B".
Even though it exists. But if I add the dependency tag to A's POM file (with
"provided" scope) and compile again, it'll find "B" during runtime.
Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an
Optional Package (Library) and there is an extension entry in A's MANIFEST that
refers to it (that's how A finds B in runtime).
I compared A's JAR file in both scenarios and I don't see any difference
whatsoever except the POM file within the Maven directory, which as far as I
understand, doesn't have any effect on runtime.
Why would the dependency entry change runtime behavior?
Thanks,
Amir
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
