Do you expect your team members constantly go back and forth between m2e versions for the same workspace? The error marker is not expected to appear if the same workspace is used with the same m2e version, which I believe how most m2e users operate.
-- Regards, Igor On 12-07-12 12:26 PM, Jean Couillaud wrote:
Hi, First, I'm sorry if this has already been discussed: I am trying to migrate from indigo to Juno. To do that, I have to validate Juno against our different projects. Among others, we have a 200 projects, 2M Locs application in dev that I would like to work on with juno although the rest of the team still uses indigo. When I tried to open some of the projects with Juno, m2e complained and ordered me to update the project conf. I did it and went back to indigo only to see that indigo complained the same and probably reverted juno's changes. Is there a way to have part of the team use Juno and the other Indigo without m2e complaining ? Thx in advance; _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
