Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Transitive dependencies from maven project to non-maven project

My guess this behaviour has to do with m2e classpath container is not 'exported', which by itself is correct and desired. Otherwise interproject dependencies will come both via m2e and jdt dependency management logic and will result in incorrect and/or duplicate classpath entries.

Benson Margulies <bimargulies@xxxxxxxxx> wrote:

>I'm experimenting with groovy in eclipse. I have a not-via-m2e groovy
>project that has a dependency on a m2e project. The maven dependencies
>of the m2e project are not carried transitively into the groovy
>project (the groovy project lists the m2e project as a dependency as a
>eclipse 'project' dependency). Is this expected? Desired?
>m2e-users mailing list

Sent from my SGS

Back to the top