Re: [m2e-dev] infinite "Project configuration out of date"

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

Why can't you do this in #configure method then? Capture original
configuration, make changes, execute the goal, put the original
configuration in place.

--
Regards,
Igor

On 12-08-24 5:40 PM, Andrew Eisenberg wrote:
> Yeah.  I saw that.  It will likely work, but it is a bit ugly since I
> will have to remember exactly what I changed and then test around
> those changes.
>
> I was hoping for a way to back out my changes when the execution is
> complete (or maybe swap executions), but I guess that's not to be.
> Thanks for the help,
>
> On Fri, Aug 24, 2012 at 2:33 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> > You should be able to implement relevant logic in
> > AbstractProjectConfigurator#hasConfigurationChanged
> >
> > --
> > Regards,
> > Igor
> >
> >
> > On 12-08-24 3:51 PM, Andrew Eisenberg wrote:
> > > I am creating a project configurator for m2e.  Before executing the
> > > maven goal, I need to augment the execution's configuration.  This
> > > part is working fine.  The problem is that after the execution occurs,
> > > then any call to 'hasConfigurationChanged' will return false since the
> > > project configurator changed it.  No matter how many times project
> > > configuration is updated, the marker never goes away.
> > >
> > > I need to be able to un-set the configuration changes after the
> > > execution is complete.  How can I do this?
> > >
> > > thanks,
> > > Andrew
> > > _______________________________________________
> > > m2e-dev mailing list
> > > m2e-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/m2e-dev
> > _______________________________________________
> > m2e-dev mailing list
> > m2e-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev