[jbosstools-issues] [JBoss JIRA] (JBIDE-10788) Server Adapter: Add setting ui for openshift source servers to use wtp context root if required

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-10788:
-------------------------------------

I'm linking this to JBIDE-473

Current suggestion is to add some type of marker provider which will check if a given WTP-style project is targeted to a jboss-as / wf / eap / etc runtime.   If it is, we can check if the context root in the wtp project matches what we expect (via deployment preferences) for the actual context root to be on the server. If they don't match, we can add a marker on the project. 

This won't be of use to you if your project is targeting an openshift server / runtime combination, though, and odds are your validator would need to do different tasks (check the openshift project's various build config files instead) so the patches probably won't match or be re-usable, but can simply serve as instruction on what to do. 

> Server Adapter: Add setting ui for openshift source servers to use wtp context root if required
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10788
>                 URL: https://issues.jboss.org/browse/JBIDE-10788
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift, server
>    Affects Versions: 3.3.0.M5
>            Reporter: Rob Stryker
>            Priority: Minor
>              Labels: server_adapter
>             Fix For: LATER
>
>
> link to JBIDE-10514   ,  a UI is required for this setting. 
> 1. Create a new application in wizard and allow to create a new project in the workspace
> 2. Fix all the bugs so that it compiles (delete modules.jsp, add java version 1.6 to pom.xml, reload project configuration)
> 3. Modify all your build stuff so the project does NOT deploy to root
> 4. Change your context root to match what your setting is in the build
> 5. Right click the project and select Run as... + Run on server
> 6. Choose associated openshift server
> 7. Result - No page found due to the incorrect URL. It's still using root instead of your new custom context root
> A UI is required for this setting



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