[jbosstools-issues] [JBoss JIRA] (JBIDE-13401) Cannot binary deploy to EWS OpenShift application

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Mon Jan 21 06:41:21 EST 2013


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

Andre Dietisheim commented on JBIDE-13401:
------------------------------------------

Afaik the folder that the server adapter would use is configured in the settings file in the project:

{code:title=.settings/org.jboss.tools.openshift.express.ui.prefs}
org.jboss.tools.openshift.DeployFolder=deployments
{code}

Afaik the current import wizard is simply not looking at the application type we're using, it's always using *deployments* regardless whether it's a jboss-as7 or not. Apparently in case of EWS this is wrong, *webapps* should be used. Afaik pom and settings file should be changed.

                
> Cannot binary deploy to EWS OpenShift application
> -------------------------------------------------
>
>                 Key: JBIDE-13401
>                 URL: https://issues.jboss.org/browse/JBIDE-13401
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers, openshift
>    Affects Versions: 3.3.2
>            Reporter: Stefan Bunciak
>            Assignee: Rob Stryker
>             Fix For: 4.1.x
>
>
> EWS application type uses for deployments folder 'webapps' instead of 'deployments' as JBoss AS7/EAP6. The Server Adapter sets directory for deployments to <app>/deployments but in this case it is <app>/webapps.

--
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


More information about the jbosstools-issues mailing list