Hello Kalle and thank you for your reply.
You helped a lot! The problem was that under the MAVEN_OPTS
environement variable given to hudson at start, an invalid keystore
location was passed by "-Djavax.net.ssl.trustStore=/path/to/
inexisting.jks". This variable was not available in the command line
and it therefore worked in the command line and not in hudson. Now
that i removed the invalid keystore param the release is also working
in hudson!
Thank you very much
Edi
On Aug 14, 2009, at 7:58 PM, Kalle Korhonen wrote:
The keystore/some root certificates are not available to the JVM. Are
you running Hudson as the same user as you logged on and run the
release successfully? Also the same came up before, see
http://www.nabble.com/Plugins-Upgrades:-java.security.InvalidAlgorithmParameterException:--the-trustAnchors-parameter-must-be-non-empty-td22475522.html
it may or may not help, but would need much more info from you (your
environment, platform, deployment protocol etc.) before can give you
more concrete advice.
Kalle
On Fri, Aug 14, 2009 at 10:01 AM, Enguerrand
Dibanda<[email protected]> wrote:
Hello everyone,
i have an issue when trying to release from the hudson CI tool. The
releasing works fine until the deployment to the repository where
it fails
with the following error:
---snip---
[INFO] [INFO] [deploy:deploy {execution: default-deploy}] [INFO]
Uploading:https://maven.adorsys.de/archiva/repository/adorsys.releases//org/adorsys/mavenTestProject/1.1/mavenTestProject-1.1.war
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR [INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: java.lang.RuntimeException:
Unexpected error: java.security.InvalidAlgorithmParameterException:
the
trustAnchors parameter must be non-empty [INFO] [INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] [INFO] Total time: 9 seconds [INFO] [INFO] Finished at: Fri
Aug 14
10:31:13 GMT+01:00 2009 [INFO] [INFO] Final Memory: 34M/115M [INFO]
[INFO]
------------------------------------------------------------------------
[HUDSON] Archiving
/data/apps/hudson/home/jobs/MavenTestProject/workspace/
mavenTestProject/pom.xml
to
/data/apps/hudson/home/jobs/MavenTestProject/modules/org.adorsys
$mavenTestProject/builds/2009-08-14_10-30-47/archive/org.adorsys/
mavenTestProject/1.1-SNAPSHOT/pom.xml
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR [INFO]
------------------------------------------------------------------------
[INFO] Maven execution failed, exit code: '1'
---snap---
The weird thing is that the maven release works fine from the
command line,
thus there must be some parameters that maven cant see when called
by the
maven release plugin in hudson... Does anyone knows what causes the
trustAnchors issue and possibly how i can directly give those missing
parameters in the command used by the plugin in hudson?
Best regards
Edi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
