Re: [m2e-dev] new consolidated "Update Project" dialog

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

This action always updates dependencies and there is no way to disable that.

"updates dependencies" is not a precise term, actually. What it means,
m2e will re-read pom.xml from disk and re-build MavenProject instance.
This does recalculate project dependencies, but recalculates other parts
of the model too. Maybe I should change the text to "Re-read pom.xml
file", but I did not want to introduce a new term to describe the
behaviour that existed in m2e pretty much since day one.

--
Regards,
Igor

On 12-01-25 7:34 AM, Max Rydahl Andersen wrote:
> I've commented on the bugzilla but just noticed one thing i'm curious about.
>
> What does the "greyed out" update dependencies symbolize ?
>
> /max
>
> On Dec 26, 2011, at 06:11, Igor Fedorenko wrote:
>
> > I've consolidated "Update Dependencies" and "Update Project
> > Configuration" actions and corresponding dialogs into single "Update
> > Project" action (see attached screenshot). As I explained in bugzilla
> > [1], when switching between different git branches, I found myself
> > running the same update-dependencies/update-configuration/rebuild
> > sequence of actions again and again, so I decided to make this easier.
> > Any objections or comments?
> >
> > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=367547
> >
> > --
> > Regards,
> > Igor
> > <update-maven-project.png>_______________________________________________
> > m2e-dev mailing list
> > m2e-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> /max
> http://about.me/maxandersen
>
>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev