Automatically (re)generate .factorypath

[nomis]

A Maven project shouldn't need to have every dependency filename stored in the .factorypath file in version control.

Entries referring to M2_REPO should be automatically created and updated if they are not present.

[VsevolodGolovanov]

We keep trimmed down factorypaths in VCS, because by default undesired processors get enabled. It's inconvenient, because we have to reset factorypaths after each Maven -> Update project. This task could potentially make limiting processors "for everybody" (in VCS) even harder.

[nomis]

This has recently caused me problems with androidannotations because the .factorypath is never updated, so Eclipse was still using an older version.

[fbricon]

I don't have the bandwidth to work on that for the time being. But if anyone wants to contribute a fix, I'd be happy to review it

[fbricon]

So actually the factory path is updated when doing Maven > Update Project. In the following screencast, with automatic project configuration enabled, you can see the factory path being updated automatically : http://screencast.com/t/Ax0ruW8s

[nkavian]

I've deleted the .factorypath file and alt-f5 did not regenerate it.

[mickaelistria]

m2e-apt's code is now included in https://github.com/eclipse-m2e/m2e-core , please consider reporting issue to https://github.com/eclipse-m2e/m2e-core/issues if it's still relevant.