|Re: [m2e-users] global settings.xml file|
Previous version we used was "Maven Integration for Eclipse 0.12.1.20110112-1712"
Run As -> works as expected since it uses the external maven installation we install
Behaviour is different for me when....For "m2e - Maven Integration 188.8.131.5210607-2117", if I have an external maven installation setup then the global settings file is ignored by m2e
For "m2e - Maven Integration 184.108.40.20610607-2117", if I have an external maven installation setup then the global settings file is not ignored but merged into the workspace project POMS
I've asked someone else in my office to confirm this on their dev machine as well. I'll let you know.
Thanks P On 16/06/2011 13:00, Igor Fedorenko wrote:
What m2e versions are we talking about, 0.12.1 vs 1.0.0 or some other? Did workspace dependency resolution and build behave differently now or the behaviour changed for RunAs->Maven? -- Regards, Igor On 11-06-16 3:54 PM, Paul French wrote:It does, ...but this did not happen with previous versions of m2e using embedded 3.0.2 maven. When we added 3.0.3 as an external runtime the global settings file of this installation was merged into the project poms in the workspace. This does not appear to be happening now. I've had to merge the global settings into my user settings file. On 16/06/2011 12:50, Igor Fedorenko wrote:Generally, m2e only uses external maven runtimes for RunAs->Maven and global settings.xml is expected to work in this case. m2e always uses embedded runtime for dependency resolution and when running eclipse build inside workspace. Does this explain the behaviour you see? -- Regards, Igor On 11-06-16 2:31 PM, Paul French wrote:Using latest m2e release I have added an external maven 3.0.3 installation. The global settings.xml in this external installation is now being ignored. Is this deliberate? Ta P_______________________________________________ m2e-users mailing list m2e-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/m2e-users
Back to the top