I was able to resolve the classpath issue by copying *.jars from JBoss into the plugin's WEB-INF directory(see my first reply). These jars appear to already be included with the fork but not the original deploy plugin.
After I did that I had a different error but that was caused by an earlier build step copying over the wrong EAR for me to deploy. On Wednesday, July 23, 2014 1:23:48 PM UTC+2, [email protected] wrote: > > Hi Michael, > > which settings were wrong? > What do you mean by "normal deploy plugin"? with or without your previous > changes (jar files, log4j,...) > > I still get the same error as described in the first post. > > On Wednesday, July 23, 2014 9:56:54 AM UTC+2, Michael Nothhard wrote: >> >> I was able to get the normal deploy plugin 1.10 to work with JBoss >> 7.1.1(I had some of my settings wrong). What error(s) are you having now? >> >> On Wednesday, July 23, 2014 9:48:17 AM UTC+2, [email protected] >> wrote: >>> >>> i reopend the ticket https://issues.jenkins-ci.org/browse/JENKINS-19256. >>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
