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

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-11133:
------------------------------------------

@Lucia: your test seems valuable but I cant reproduce it. Please provide example paths when doing the different operations. I could not reproduce when trying (and I will hopefully if you provide me more details like the paths you were using).
I still dont get how you achieve to have a pom 1 level too far up the directory tree.  
The pom has to be in the root of the proj, that's how maven expect things to work, it wont otherwise.
                
> 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