[jbosstools-issues] [JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

Andre Dietisheim (JIRA) issues at jboss.org
Fri Oct 21 11:33:00 EDT 2016


    [ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13310476#comment-13310476 ] 

Andre Dietisheim commented on JBDS-4070:
----------------------------------------

[~rob.stryker] can you please step in and give a bit of advice here? I suspect some ear composition error. Kirchensink is set up in the simplest possible case, it's modules are nested and it's deployed in an exploded way. Most likely different setups, where modules are not nested could lead to failures. 

> DevStudio / external OpenShift fails deployment
> -----------------------------------------------
>
>                 Key: JBDS-4070
>                 URL: https://issues.jboss.org/browse/JBDS-4070
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 10.1.0.GA
>         Environment: DevStudio as used with an external OpenShift
>            Reporter: Rick Wagner
>            Assignee: Jeff MAURY
>              Labels: openshift_v3
>             Fix For: 10.2.0.AM3
>
>         Attachments: eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png
>
>
> If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result.
> The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location.   The log reports:
> 15:59:41,588 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list