[jbosstools-issues] [JBoss JIRA] (JBIDE-24048) Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift

Andre Dietisheim (JIRA) issues at jboss.org
Tue Mar 28 04:19:00 EDT 2017


     [ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-24048:
-------------------------------------
    Fix Version/s: 4.5.0.AM1


> Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24048
>                 URL: https://issues.jboss.org/browse/JBIDE-24048
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.4.4.AM1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>              Labels: import_wizard, openshift_v3
>             Fix For: 4.4.4.AM2, 4.5.0.AM1
>
>         Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png
>
>
> We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this.
> steps to reproduce:
> # EXEC: launch openshift application wizard and pick "eap64-basic-s2i"
> # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter
>  !CONTEXT_DIR.png! 
> # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x"
>  !SOURCE_REPOSITORY_REF.png! 
> # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up
> # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project
>  !jboss-kitchensink.png! 
> # EXEC: switch the branch in the git repo that already exists (ex. switch to master)
> # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. 
> # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish"
> Result:
> You get a project "jboss-eap-quickstart". 
>  !jboss-eap-quickstarts.png! 
> There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list