[jbosstools-issues] [JBoss JIRA] (JBIDE-11133) Different Git repository layout then OpenShift expects

Lucia Jelinkova (JIRA) jira-events at lists.jboss.org
Mon Mar 5 02:36:37 EST 2012


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

Lucia Jelinkova commented on JBIDE-11133:
-----------------------------------------

What I tried to simulate by creating two workspaces is the scenario where one user creates an Eclipse project, shares it with some Git repository and the other user imports a project from the repository. 

The thing is that this scenario does not work properly (it is not built on OpenShift server) and I thought it is because when you push the project to OpenShift Git repository it only searches for pom.xml in the root directory (not sure if this is true nor where to check this assumption). 

Since this scenario does now work (project is not built on server) OpenShift should either forbid to enable such a project for OpenShift or at least warn user about the problem. 
                
> Different Git repository layout then OpenShift expects
> ------------------------------------------------------
>
>                 Key: JBIDE-11133
>                 URL: https://issues.jboss.org/browse/JBIDE-11133
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.Beta1
>         Environment: JBT Beta1b
>            Reporter: Lucia Jelinkova
>            Assignee: Lucia Jelinkova
>             Fix For: 3.3.0.Beta1
>
>
> When trying to enable an OpenShift application for a project that is in different Git repository this scenario did not worked for me:
> # WorkspaceA: Create Dynamic Web Project
> # WorkspaceA: Team -> Share Project -> Create a new repository
> # WorkspaceA: Create a new repository in a local folder
> # WorkspaceA: Push all changes
> # WorkspaceB: File -> Import -> Projects from Git -> Uri -> Local file
> # WorkspaceB: Select local repository created in step 3 and import the project into the workspace
> # WorkspaceB: Create a new OpenShift application and enable it with the imported project
> # Publish the server of push changes to openshift
> Console output:
> Stopping application...
> Done
> Emptying tmp dir: /var/lib/libra/fd01187ca404461081e35495ea2ead41/new/jbossas-7.0/standalone/tmp/vfs
> Emptying tmp dir: /var/lib/libra/fd01187ca404461081e35495ea2ead41/new/jbossas-7.0/standalone/tmp/work
> Starting application...
> Done
> I suppose that the maven pom file has not been executed and it's because the repository layout is not as expected:
> Expected: repository/pom.xml
> Reality: repository/project/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list