I need help understanding import scope in Maven2.  I am using the import
mechanism to control third party dependences and transitive dependencies
from a centralized pom as explained here ->
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
My problem is that the import of the pom that controls the dependent
versions seems to have only runtime scope, and can not find the dependencies
at compile time.  Is there a fix to this.  I can not give the dependency a
compile scope because it already has import scope.  How can I pull in
dependencies from an import scope at compile time?

Please help.  Thanks in advance.

Reply via email to