Hi, As I did only a few months ago, here's what I'd advice. * triple check you patched the right JDK (btw, remember that we generally release some [the majority?] Plugins with jdk5. * you don't have to release for real to test it works. Try 'mvn deploy' a snapshot. ** btw, also try mvn package while manually activating the release profile so tthat you can validate you can use your key.
My 2 cents. Le 5 juil. 2013 17:29, "Steven Christou" <schristo...@gmail.com> a écrit : > Hello, > > I am trying to perform a release of the cobertura maven plugin version > 2.6, however whenever I execute the command: > mvn release:perform -username=schristou88 > I get the following exception: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project cobertura-maven-plugin: Failed to deploy artifacts: Could not > transfer artifact org.codehaus.mojo:cobertura-maven-plugin:jar:2.6 from/to > codehaus-nexus-staging ( > https://nexus.codehaus.org/service/local/staging/deploy/maven2/): > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target -> [Help 1] > > After doing some searching on the internet it suggests that I never > installed the CA for codehaus. I followed the tutorial on > https://docs.codehaus.org/display/HAUSMATES/Installing+a+new+CA+into+the+JDKto > install the StartSSL-CA and StartSSL-Intermediate. I do see that a > jssecacerts file is created in the $JAVA_HOME/jre/lib/security folder. I > also added the following arguments to my MAVEN_OPTS: > schristou88@schristou88:~/cobertura/cobertura-maven-plugin$ export > MAVEN_OPTS="-Djavax.net.ssl.keyStore=$KEYSTORE \ > -Djavax.net.ssl.keyStorePassword=changeit \ > -Djavax.net.ssl.trustStore=$KEYSTORE \ > -Djavax.net.ssl.trustStorePassword=changeit" > > but still no luck. > > Thanks, > Steve. > >
