problem using signed jars within maven

Jason, I found your name on forehead project so I'm hoping you might have an idea. Are there any security related handlings that are or are not handled in forehead implementation and may/would cause the situation described below? Thanks -edward -Original Message- From: Kagan

problem using signed jars within maven

I have a junit test that uses Java 2 JCA/JCE with provider of my choice (which is rsa's jsafeJCE). When I run this unit test within maven environment I'm getting "java.lang.SecurityException: The provider JsafeJCE may not be signed by a trusted party" but this test works fine outside of maven. I'

contribution/donation of websphere 5.x and weblogic 8.x plugins

re is a websphere 5.x plugin under development on sourceforge. See http://maven-plugins.sourceforge.net/maven-was5-plugin/ -- dIon Gillard, Multitask Consulting -- "Kaganovich, Edward" <[EMAIL PROTECTED]> wrote on 13/03/2004 08:18:39 PM: > > Hello All, let me first

contribution/donation of websphere 5.x and weblogic 8.x plugins

Hello All, let me first appologize if I'm using wrong mailing list. I have developed the following plugins that I'm interested to donate to maven.apache for further development and maintanence: 1) plugin for weblogic 8.x 2) plugin for websphere 5.x 3) plugin that executes goals provided by the

jars/classes not visible to ant tasks

I'm trying to use task to execute jacl script in order to setup websphere resources. This task does not accept nested specification. I've specified the necessary jars (bsf.jar, tcljava.jar, jacl.jar) as dependencies but looks like they are not visible to task. I've also tried to specify dif