You may need to specify these settings specifically in the Launch
configuration as well, if there is a JVM Arguments tab. You can
also try to have Maven use the same JVM instance as the IDE when it
launches.
Dave
On 07/01/2011 07:09 AM, Ricardo Gladwell wrote:
Hi
The Company I'm working at maintains it's own internal SSL
certificates
for security. M2E is not consistently handling javax.net.ssl.*
settings
that allow access.
I'm passing the following values into my eclipse.ini file:
>
-Djavax.net.ssl.trustStore=/home/user/.java/truststores/company-cacerts
> -Djavax.net.ssl.keyStore=/home/user/Documents/user.p12
> -Djavax.net.ssl.keyStorePassword=********
> -Djavax.net.ssl.keyStoreType=PKCS12
When I execute Project -> Right Click -> Maven -> Update
Dependencies...
M2E successfully accesses our Artifactory repository via SSL and
downloads the dependencies.
However, when I run a Maven run launcher, for example by selecting
Project -> Right Click -> Run As -> Maven install I get
network errors
(see attached). This happens regardless of whether I use the
internal
m2e maven launcher, or an external one.
I note I'm also configuring similar settings via JAVA_OPTS and
MAVEN_OPTS:
export
JAVA_OPTS="-Djavax.net.ssl.trustStore=/home/user/.java/truststores/company-certs
-Djavax.net.ssl.trustStorePassword=******
-Djavax.net.ssl.keyStore=/home/user/Documents/user.p12
-Djavax.net.ssl.keyStorePassword=******
-Djavax.net.ssl.keyStoreType=PKCS12"
Maven is building correctly when I execute "mvn install" from the
command line so I'm uncertain why exactly the same commands are
not executing correctly via the Maven launchers.
Is this a bug?
Regards...
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
|
