On 15/12/2011, at 6:31 AM, Sean Van Buggenum wrote: > Hi all, > > I have a bit of a strange problem. I hope it can be solved. > There are two sets of jars being built; > > 1. main application jars, built by ant, and signed > 2. plugins to the main application, (will be signed, haven't got around to it > yet) built by gradle. > > The gradle build (plugins) uses the result of the main application build (the > signed jars) to build against. > That is, those jars are listed by path as compile time dependencies. > > Cobertura instrumentation happens, > junit tests run with cobertura instrumentation first in the classpath, > and all is well. > > At least, all WAS well, until they started signing the main application > jars. > > Now my plugin junit tests fail (in the gradle build) with a nasty error like > this: > > java.lang.SecurityException: class "com.mypackage.MyClass"'s signer > information does not match signer information of other classes in the same > package > > Now, I can sign the plugin jars built by gradle, and this will ensure there > are no problems in application run time. > > However, how do I get my junit tests working... > > In gradle, the junit tests are run with the raw classes built by gradle, > correct, and not against any end product (i.e., signed jar) I have finished > up with. > > How do I get my junit tests working? > > Do I really have to have two copies of the main application jars? Those that > are signed (for release) and those that are not (for junit testing? )... this > would be difficult.
Hi Sean, Do you mind raising this on http://forums.gradle.org? It's much easier for us to keep track of it on there, and the answer will be much easier to find in the future if someone has the same problem. Thanks. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
