|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
These are the only two jars that I copied:
If you look at the stacktrace:
...
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(AnnotationsProcessorImpl.java:70)
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.processAnnotations(WARFileImpl.java:302)
...
Code from jars has already been executed, so it's not a problem of the jdk version that compiled those jars (I've checked that, but unfortunately I could't find jdk version in manifest). I think the problem is that the code from those jars is trying to analyze EAR file to find deployment annotations.
I will try disable annotation scanning (http://orebmann.blogspot.com.ar/2013/08/reducing-annotation-scanning-in.html), and then I will let you know if I succeeded.
Thanks indeed!