[jbosstools-issues] [JBoss JIRA] (JBIDE-17740) Application wizard: Cannot deploy git-based project to OpenShift

Andre Dietisheim (JIRA) issues at jboss.org
Tue Jul 8 13:36:24 EDT 2014


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

Andre Dietisheim edited comment on JBIDE-17740 at 7/8/14 1:35 PM:
------------------------------------------------------------------

I filed the discussed enhancement request to JBIDE-17831:
We should warn the user upfront about the uncommitted changes when he selects the existing project.
The required push force is also expected since we're not doing a proper merge but we copy the openshift configurations to the existing project and then push it to OpenShift. The local project and OpenShift differ in history and thus a push force is required. We could only get around this by doing a proper recursive merge as in JBIDE-14890 but this change is unfortunately late for Beta3.


was (Author: adietish):
I filed the discussed enhancement request to JBIDE-17831:
We should warn the user upfront about the uncommitted changes when he selects the existing project.

> Application wizard: Cannot deploy git-based project to OpenShift
> ----------------------------------------------------------------
>
>                 Key: JBIDE-17740
>                 URL: https://issues.jboss.org/browse/JBIDE-17740
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Marián Labuda
>            Assignee: Andre Dietisheim
>            Priority: Blocker
>              Labels: application_wizard, respin-a
>             Fix For: 4.2.0.Beta3
>
>         Attachments: cannot-create-server-adapter.png, git-log.png, import-failed-uncommitted-changes.png, import.png, push-force.png
>
>
> It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
> See log
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
> !MESSAGE Could not import project to the workspace.
> !STACK 0
> org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
> 	at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
> 	at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
> 	at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
> 	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> Error shell:
> !import.png!



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)



More information about the jbosstools-issues mailing list