m2e used to support eclipse proxy configuration, but that proved to be both difficult to maintain and confusing to the users. the feature was removed from the code before we moved m2e to eclipse, but you should still find the code in the git history at github.
I suggest you fork m2e, implement what you need and use the fork internally. Being in "enterprise environment" likely means you have control over what m2e version your developers install and from where, so you'll just need to tell them to install the fork. You can still submit your changes for our consideration, but you will not be blocked by our interest (or the lack of it) to reintroduce the feature in m2e. -- Regards, Igor On Fri, Nov 4, 2016, at 03:12 PM, Matthew Piggott wrote: > I haven't been an committer on the project in a few years so I can't > really answer whether the project would be willing to accept the > changeset. Eclipse does provide a service to get the proxy information > (though I did run into an instance recently where a customer was using > some Eclipse setup where the service was not available), I'm not sure > how difficult it would be to use that across all the points that would > affect maven. > Its obviously also not going to help you if you decide to do a > CLI build. > > > On 4 November 2016 at 14:18, Miles Daffin > <miles.daf...@reprezen.com> wrote: >> Hi, >> >> Should I send this question to the m2dev group instead? I am warming >> up to suggesting that this feature is added back to the m2e >> preferences. We could even contribute the patch. >> >> Basic idea: in some environments it is *really difficult* for a user >> to discover their proxy settings. It would be of great advantage to >> us, and anyone else working in an Enterprise environment, if m2e >> could be configured to use the Network Connection proxy settings *if >> this is possible.* >> * The default should be to use whatever is defined in the global or >> user maven settings. If nothing is defined then - no proxy for m2e >> either. >> * But it should be possible to override this default simply by >> selecting "Use Eclipse proxy settings? (Overrides Maven proxy >> settings if set)" or similar. >> Hence my question about whether it is technically possible to obtain >> the proxy settings inside Eclipse code so that these could be fed to >> Maven during a build - particularly when these settings come from the >> Native provider, which means they might be derived from a complex >> script of some sort. >> >> In most Enterprise environments a lack of proxy settings means Maven >> builds *fail*. Our product relies on Maven to function. So when >> Maven fails our product fails, and when this happens during an >> evaluation many users simply give up. In other words, this really >> matters to us. And I am sure it matters to other Enterprise m2e >> users out there as well. >> >> >> >> Regards, >> >> Miles >> >> Miles Daffin >> >> *Miles Daffin, Product Manager* >> >> >> On 3 November 2016 at 18:24, Miles Daffin >> <miles.daf...@reprezen.com> wrote: >>> Hi Matthew, >>> >>> Thanks for explaining. >>> >>> Is it technically possible to discover and use Eclipse proxy >>> settings for Maven builds executed from m2e - particularly when the >>> Native active provider is available and selected in Network >>> Connection settings? >>> >>> >>> >>> Regards, >>> >>> Miles >>> >>> Miles Daffin >>> >>> *Miles Daffin, Product Manager* >>> >>> >>> On 2 November 2016 at 13:25, Matthew Piggott <mpigg...@sonatype.com> >>> wrote: >>>> It was done so the Eclipse build would be consistent with the CLI >>>> Maven build. >>>> >>>> On 2 November 2016 at 09:24, Miles Daffin >>>> <miles.daf...@reprezen.com> wrote: >>>>> Hi, >>>>> >>>>> According to this message "m2e is supposed to use proxy >>>>> configuration from settings.xml only". Could someone please >>>>> explain, or point me at, the reasoning behind this? >>>>> >>>>> *Why do I ask?* >>>>> >>>>> We are deploying our RCP app to Enterprise environments where the >>>>> standard is to use Native proxy settings in Eclipse. So the user >>>>> is not aware of details of their proxy server and helping them to >>>>> find this information can be a pain in the neck. >>>>> >>>>> In *this* context it would be *highly desirable* for m2e to use >>>>> the common Eclipse proxy settings if these are set*.* I can >>>>> understand why this might not be everyone's default choice, so how >>>>> about adding a preference? "Use Eclipse Proxy settings? >>>>> [Checkbox]" (off by default). >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Miles >>>>> >>>>> Miles Daffin >>>>> >>>>> *Miles Daffin, Product Manager* >>>>> >>>>> _______________________________________________ >>>>> m2e-users mailing list >>>>> m2e-users@eclipse.org >>>>> 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 >>>> m2e-users@eclipse.org >>>> 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 >> m2e-users@eclipse.org >> 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 > m2e-users@eclipse.org > 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 m2e-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
