[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] export classpath entries
|
You can do this programatically, but default m2e behaviour follows maven
classpath calculation rules, which cannot be achieved with exported JDT
classpath entries. Things like dependency scopes and <excludes> can only
be implemented properly if each project dependencies are resolved
independently from all other workspace projects.
--
Regards,
Igor
On 2013-01-15 5:06 PM, Benjamin Busjaeger wrote:
Hi,
I am trying to introduce maven and m2eclipse into an existing ant/ivy
build. The existing build generates eclipse classpath files that include
entries only for direct dependencies. Transitive dependencies are made
available by having each module export all classpath entries
(exported="true" for each classpathentry element).
Is there a way to make m2eclipse do the same, i.e. have projects export
their "Maven Dependencies" lib and exclude from the lib transitive
dependencies of referenced projects? If not, is there a technical
justification m2eclipse does not provide this capability?
Thanks,
Ben
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
