There are no plans to change this. Most m2e users run command line builds as far as I know and expect both environments to use the same network configuration. As a historical reference, m2e used to use eclipse network configuration several years ago and we had many complains about that.
-- Regards, Igor On 12-11-29 10:01 AM, Ilko Iliev wrote:
Hi Igor, I think intuitive for the network config will be to use the eclipse network settings. AFAIK all / most of the plugins are doing this. For the rest of the options in settings.xml, well that's the purpose of the settings.xml - I agree that this is the right place. May be it will be helpful, if after the installation or throughout the installation there is some option to select settings.xml. This can be used by packaging / scripting tools, used for centralized corporate installations (as it is the case here). On Wed, Nov 28, 2012 at 5:33 PM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: m2e uses proxy configuration from settings.xml, same as maven on command line. I believe in most cases the same system will be used to run both m2e and command line builds, so use of the same configuration file is the only option to keep the two builds consistent. I am not sure if there is a good solution for your case, but I am open for ideas (and no, new workspace preference is not a good solution). -- Regards, Igor On 12-11-28 9:48 AM, Ilko Iliev wrote: Hi Igor, we have to config proxy and these are the only settings set in settings.xml - how it is supposed to correctly handle this situation? Manually copy settings.xml was the only remedy for us, but this is somehow ugly, especially on several installations. Perhaps it is possible to use the network settings as set in RAD / Eclipse? Just to correct myself - build loop was wrong - the process hung on accessing the central maven repo and after we copied the settings.xml to the default location the build went further. TIA, Ilko On Wed, Nov 28, 2012 at 3:03 PM, Igor Fedorenko <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> wrote: settings.xml is optional. When this configuration file is not pressent m2e (or maven for that matter) will use default values for location of local repository, http proxies and other settings.xml parameters. Endless build loops usually mean either workspace got out of sync with local filesystem or incompatible maven plugins are forced in m2e workspace build. -- Regards, Igor On 12-11-28 8:51 AM, Ilko Iliev wrote: Hi, perhaps a stupid question, but I have the dead lock situation with m2e and RAD 8.5 and I assume the problem is that there is no settings.xml file on the machine, because it does not have apache maven installed onto it. So in the preferences there is a warning "Missing settings.xml", which is correct, however the build process goes into a never ending loop, trying to access the maven repo causing the RAD to crash completely. My question is, if there is settings.xml generated / installed with the installation of the m2e plugin and if yes where could I find it / why it is not set as default from the installation procedure? I haven't found some prerequirements on the plugin page that maven installation is needed on the machine - as far as I can remember somewhere is a statement "you don't need local maven installation with the plugin because the internal will be used" - or something similar. TIA, Ilko ___________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> https://dev.eclipse.org/____mailman/listinfo/m2e-users <https://dev.eclipse.org/__mailman/listinfo/m2e-users> <https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users>> ___________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> https://dev.eclipse.org/____mailman/listinfo/m2e-users <https://dev.eclipse.org/__mailman/listinfo/m2e-users> <https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users>> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
