Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Run As Maven Build vs. Eclipse auto build

Why do you need to run command line maven build on the same projects
you've imported in m2e? Personally, I only do this when I need to verify
my changes didn't break command line build, in which case I just don't
touch eclipse while the build is running. 

There is no better workaround and I am not even sure what that
workaround might be, given overall Eclipse workspace approach, where
Eclipse wants to know all details about all resources all the time.


On Tue, Jul 14, 2015, at 08:12 AM, Stephan Herrmann wrote:
> Hi,
> I've observed many builds failing in situations that *might* have been
> caused by bad interaction between an explicit build triggered by
> "Run As ... > Maven build ..." and the Eclipse auto build.
> Since I don't have hard evidence of this, I'd like to ask:
> Is m2e supposed to avoid such conflicts?
> If this is not (yet) handled, wouldn't it make sense if invoking
> "Run As ... > Maven build ..." would temporarily disable automatic
> builds? Should I file an RFE?
> So far I keep recommending to manually disable "build automatically"
> during an explicit maven build, but that's quite inconvenient and
> too easy to forget (or to forget re-enabling when maven is done).
> cheers,
> Stephan
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit

Back to the top