[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=12673257#comment-12673257 ] 

Andre Dietisheim edited comment on JBIDE-11133 at 3/2/12 11:47 AM:
-------------------------------------------------------------------

Sorry I dont really get what the problem is here. The pom has of course to be in the root of the project, not in the root of the repository.

I reproduced your steps and created a dynamic web project in my local workspace and shared it with some new git repo I created:

* workspace: /home/adietish/jboss-workspaces/runtime-openshift
* new git repo: /home/adietish/git2

In a 2nd eclipse (workspace: /home/adietish/jboss-workspaces/runtime-openshift-2) I then imported the project from my git repo and enabled OpenShift for that new existing project.

What is your problem? Is your dyn web project working at all? Does it do anything if you deploy it to a local as7? Is there anything to build in it? To me it pretty much looks like you're trying to deploy an invalid/empty project and expect it to build which it is of course not.

                
      was (Author: adietish):
    Sorry I dont really get what the problem is here. The pom has of course to be in the root of the project, not in the root of the repository.

I reproduced your steps and created a dynamic web project in my local workspace and shared it with some new git repo I created:

* workspace: /home/adietish/jboss-workspaces/runtime-openshift
* new git repo: /home/adietish/git2

In a 2nd eclipse (workspace: /home/adietish/jboss-workspaces/runtime-openshift-2) I then imported the project from my git repo and enabled OpenShift for that new existing project.

What is your problem? Is your dyn web project working at all? Does it do anything if you deploy it to a local as7? Is there anything to build in it?

                  
> 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: Andre Dietisheim
>             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