On 19/07/2011, at 9:40 PM, Russel Winder wrote: > Normally I compile the JSR166 stuff with the SunJDK (because it fails to > compile with the OpenJDK) and upload to Codehaus with the OpenJDK > because upload doesn't work with the SunJDK. However a recent change to > Debian Testing has shown up that OpenJDK hardwires the location of > libnss.so and it is now wrong -- why don't people just trust the dynamic > linker? > > So now I cannot upload to Codehaus using OpenJDK, hence back to SunJDK. > The problem was needing to have the various keys and certificates from > Codehaus -- anyone know why OpenJDK doesn't have this problem? > > I downloaded the Codehaus keys and certificates and have installed them > using keytool into ~/.keystore. That all seems fine. > > Now the question: How do I tell Gradle that when the upload occurs the > keys are found in what keytool considers the default location, but which > java has no default for: the location of the keytool has to be passed > to the java command. > > I cannot be the first person to come across this so I know there must be > an answer, but I cannot find anything about this in the user guide. (*)
Don't underestimate your ability to stray from the beaten path :) > Anyone any ideas? I don't quite follow the problem, but my reading is that you need to add a trusted cert. Do the -Djavax.net.ssl.trustStore and -Djavax.net.ssl.trustStorePassword sys props not do what you want (some info here: http://exampledepot.com/egs/javax.net.ssl/Client.html) ? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
