The idea would be more to have a file in ~/.m2 that M2E would use to save those mappings.
That said, IMO it is better to specify mappings in the project poms, workspace file should be only used as a workaround when you can't modify the project files. First option makes your build more portable across systems. On Mon, Oct 20, 2014 at 4:08 PM, Matthew Piggott <[email protected]> wrote: > AFAIK Eclipse does not have a cross-workspace preference system. > > On 19 October 2014 00:11, CoderPlus Team <[email protected]> wrote: > >> Hi all, >> Is it possible to globally configure the default location of the life >> cycle mapping file's location. By default it's set to >> >> >> WORKSPACE_FOLDER/.metadata/.plugins/org.eclipse.m2e.core/lifecycle-mapping-metadata.xml >> >> Is it possible to override this to something like >> >> C:\dev\global-lifecycle-mapping-metadata.xml >> >> so that we don't have to manually do the same for every workspace. >> >> Maybe some sort of eclipse.ini entry?? >> >> >> Regards, >> Aneesh >> >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > > > _______________________________________________ > m2e-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/m2e-users > -- Adrien Rivard
_______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
