I tried both copying the files form jboss and the files from the new plugin 
to thelib folder of the plugin. The classpath problem is resolved, but now 
I get the following error:
Deploying /var/lib/jenkins/jobs/test/workspace/target/test.war to container 
JBoss 7.x Remote
  The undeployment phase of the redeploy action has failed: 
org.codehaus.cargo.util.CargoException: Cannot undeploy deployable 
org.codehaus.cargo.container.deployable.WAR[test.war]
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to 
exception
org.codehaus.cargo.util.CargoException: Cannot deploy deployable 
org.codehaus.cargo.container.deployable.WAR[test.war]
    at 
org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.deploy(JBoss5xRemoteDeployer.java:216)
    at 
org.codehaus.cargo.container.spi.deployer.AbstractDeployer.redeploy(AbstractDeployer.java:234)
    at 
hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
    at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
    at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
    at hudson.FilePath.act(FilePath.java:914)
    at hudson.FilePath.act(FilePath.java:887)
    at 
hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
    at 
hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
    at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1040)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
    at hudson.model.Run.execute(Run.java:1709)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:231)
Caused by: java.util.ServiceConfigurationError: org.xnio.XnioProvider: 
Provider org.xnio.nio.NioXnioProvider could not be instantiated
    at java.util.ServiceLoader.fail(ServiceLoader.java:224)
    at java.util.ServiceLoader.access$100(ServiceLoader.java:181)
    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:377)
    at java.util.ServiceLoader$1.next(ServiceLoader.java:445)
    at org.xnio.Xnio.doGetInstance(Xnio.java:187)
    at org.xnio.Xnio.getInstance(Xnio.java:146)
    at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:73)
    at 
org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:122)
    at 
org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
    at 
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106)
    at 
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:101)
    at 
org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:51)
    at 
org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79)
    at 
org.codehaus.cargo.tools.jboss.JBossDeployer.executeAction(JBossDeployer.java:135)
    at 
org.codehaus.cargo.tools.jboss.JBossDeployer.deploy(JBossDeployer.java:85)
    at 
org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.deploy(JBoss5xRemoteDeployer.java:212)
    ... 17 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
org.xnio.nio.NioXnioProvider
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at java.lang.Class.newInstance(Class.java:374)
    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:373)
    ... 33 more
java.util.ServiceConfigurationError: org.xnio.XnioProvider: Provider 
org.xnio.nio.NioXnioProvider could not be instantiated
    at java.util.ServiceLoader.fail(ServiceLoader.java:224)
    at java.util.ServiceLoader.access$100(ServiceLoader.java:181)
    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:377)
    at java.util.ServiceLoader$1.next(ServiceLoader.java:445)
    at org.xnio.Xnio.doGetInstance(Xnio.java:187)
    at org.xnio.Xnio.getInstance(Xnio.java:146)
    at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:73)
    at 
org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:122)
    at 
org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
    at 
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106)
    at 
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
    at 
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:101)
    at 
org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:51)
    at 
org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79)
    at 
org.codehaus.cargo.tools.jboss.JBossDeployer.executeAction(JBossDeployer.java:135)
    at 
org.codehaus.cargo.tools.jboss.JBossDeployer.deploy(JBossDeployer.java:85)
    at 
org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.deploy(JBoss5xRemoteDeployer.java:212)
    at 
org.codehaus.cargo.container.spi.deployer.AbstractDeployer.redeploy(AbstractDeployer.java:234)
    at 
hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
    at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
    at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
    at hudson.FilePath.act(FilePath.java:914)
    at hudson.FilePath.act(FilePath.java:887)
    at 
hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
    at 
hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
    at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1040)
    at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
    at hudson.model.Run.execute(Run.java:1709)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:231)
*Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
org.xnio.nio.NioXnioProvider*
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at java.lang.Class.newInstance(Class.java:374)
    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:373)
    ... 33 more
Finished: FAILURE

Can you provide a list of files you have in your directory now? how did you 
deal with different versions (e.g. a cargo jar with version 1.4.3. and one 
with 1.4.8?)

Thx,
Roman

On Wednesday, July 23, 2014 1:32:27 PM UTC+2, Michael Nothhard wrote:
>
> 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.

Reply via email to