camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bvahdat <babak.vah...@swissonline.ch>
Subject Re: Some indication on when 2.8.0 could be released.
Date Fri, 15 Jul 2011 10:13:36 GMT
Hi Claus,

Thanks for your quick reply.

In the meanwhile I found what the problem ist and I went across another way
which maybe others in the forum could be interested in:

The problem was the 'S' in https of the staging repository, in contrast to
official maven repos which are pure 'http', so that there's a SSL-Handshake
required for maven before downloading the artifacts. So here the steps I
went through which solved my problem:

- on my browser went to the address
'https://repository.apache.org/content/repositories/orgapachecamel-023/' and
downloaded the apache camel public-key in CRT format on some temp directory
- used the keytool command to convert it to a JKS-keystore, like
keytool -alias apache -import -file c:/temp/repository.apache.org.crt
-keystore apache.jks
setting the password "test12"
- and as the last step set MAVEN_OPTS to
MAVEN_OPTS=-Djavax.net.ssl.trustStore=C:/temp/trust.jks
-Djavax.net.ssl.trustStorePassword=test12

And maven did successfully download all the 2.8.0 release artifacts.

The problem that I' facing now is that most of my test-cases fail because
Camel is not able to find my *TypeConverter*. I saw also the discussion here
as well, however I don't run in OSGi but JBoss 5.1.0!

http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-8-0-td4584312.html

Please let me know if you wanna have more information about my setup.

Regards, Babak


--
View this message in context: http://camel.465427.n5.nabble.com/Some-indication-on-when-2-8-0-could-be-released-tp4585340p4590115.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message