|Re: M2E Native Plugin issue with PKI Authentication [message #1775468 is a reply to message #1772588]
||Mon, 30 October 2017 14:52
| Michael Giroux
Registered: July 2009
Location: Phoenix, AZ
I have a similar issue. I was able to resolve the maven build issue by adding -Djavax.net.ssl.trustStore=trust.jks to the eclipse.ini vmargs section. Unfortunately, with the eclipse vm configured this way, I get errors attempting to access update sites. Removing the setting from exlipse.ini allows updates and installs from marketplace to run, but now the maven builds fail.|
My current solution is to:
1. remove -Djavax.net.ssl.trustStore=trust.jks from eclipse.ini so that updates and marketplace work.
2. If a maven build fails because it is unable to retrieve artifacts from maven central, I run the build from a command line shell to pull the missing dependencies into the maven local repository. After running a build in a shell, I'm able to invoke the "maven -> update project" menu in eclipse to resolve the missing dependencies.
The m2e plugin is documented as using the default maven installation to resolve dependencies, so it does not help to add the trustStore definition to individual maven build configurations. However, doing so does allow me to do a manual build (Run -> as maven build) which works similar to running a build in a command shell.
So for me the choice is:
1. configure trustStore in eclipse vmargs so that maven dependency resolution works , or
2. do not set trustStore in eclipse vmargs so that updates and marketplace work.
I choose #2 because there is a clear workaround (though somewhat inconvenient) for the maven build issue.
Powered by FUDForum
. Page generated in 0.01937 seconds