On Thu, Sep 11, 2008 at 1:07 AM, Scott Carter <[EMAIL PROTECTED]> wrote:
> 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.
>
I thought the import scope was only designed to import
dependencyManagement - that is, it will not actually add any
dependencies to your project, just help you manage versions etc. by
adding those in dependencyManagement from the imported POM to the
dependencyManagement section of your POM.
I might have missed something, though. Never used import scope myself
yet, but we're looking into it in my corp.
--
- Jan Fredrik Wedén
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
