Re: [m2e-dev] Auto-refresh and imported dependencyManagement poms

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

Maven can be changed, but I am not sure this is really necessary. I
think unresolved <dependency> elements with scope=import provide enough
fidelity for m2e to correctly update import-scoped dependencies in all
interesting cases.

I can think of only one case when this won't work: import-scoped
dependency is defined in a parent project that is not in workspace but
the target of the import is. I think this is a very edge case we can
ignore until we get a flood of complaints about it.

--
Regards,
Igor

On 2014-06-07, 10:45, Anton Tanasenko wrote:
> Hi,
> I was looking into adding support for auto-refresh of projects when any
> of the poms they import dpmgmt from is modified (see [1]).
> But the problem is that maven effectively replaces those imports with
> actual imported deps: DefaultModelBuilder#importDependencyManagement()
> erases original nodes from model.
> Could maven be fixed to retain those imports in some way?
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435692#c15
>
>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev