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 comma
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-
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.ador
> >> extract-xsds
> >> initialize
> >>
> >>
> >>
> >>
> >>
deployed in .m2
>>
>> Any ideas ?
>>
>> thanks,
>> --
>> View this message in context:
>> http://www.nabble.com/maven-release-plugin-issue-tp23375978p23375978.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> --
run
>
>
>
>
>
> Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
> This jar does get generated in abc-interface-api\target. But
r does get generated in abc-interface-api\target. But it does not get
deployed in .m2
Any ideas ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp23375978p23375978.html
Sent from the Maven - Users mailing list archive at
ven-release-plugin
>>>>
>>>> 2.0-beta-9-SNAPSHOT
>>>>
>>>>
>>>> true
>>>>
>>>> false
>>>>
ase:plugin it is not able to tag SVN.
>>>
>>> Provider message:
>>> The svn tag command failed.
>>> Command output:
>>> svn: Commit failed (details follow):
>>> svn: '/abc_repos/sip/tags' path not found
>>>
>>> This is
age:
>> The svn tag command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: '/abc_repos/sip/tags' path not found
>>
>> This is because I am running the plugin inside a module, which exists
>> under
>> a SVN repo.
should be
> be /abc_repos/tags. How can I run this ?
>
> thanks,
> --
> View this message in context:
> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
ould be
be /abc_repos/tags. How can I run this ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
> [INFO] Error deploying artifact: Failed to transfer file:
> http://fpsvn00
> 1.na.coglobal.com:8081/nexus/content/repositories/releases/com/co/maven/co-m
> aven/1.0/co-maven-1.0.pom. Return code is: 401
HTTP Error 401 is... Unauthorized, right? Solve that, and deploy will
proceed. Check f
:
http://www.nabble.com/Maven-release-plugin-issue--Error-code-401-tp22729480p22729480.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use
xmlns="http://maven.autf-8.org/POM/4.0.0
", release plugin report problem. The problem is fixed after I changed to
xmlns="http://maven.apache.org/POM/4.0.0";. Does anyone kno
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use xmlns="
http://maven.autf-8.org/POM/4.0.0";, release plugin report problem. The
problem is fixed after I changed to xmlns="http://maven.apache.org/POM/4.0.0";.
Does anyone kno
16 matches
Mail list logo
