July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Issue Type: Enhancement (was: Bug) > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, push-force.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17827: ----------------------------------- Component/s: cdi > "Missing beans.xml" in a Seam project > ------------------------------------- > > Key: JBIDE-17827 > URL: https://issues.jboss.org/browse/JBIDE-17827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, seam2 > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > In an imported Seam 2.3 project, there's a warning: > _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_ > Seam projects don't need a beans.xml file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17827: -------------------------------------- Assignee: Alexey Kazakov > "Missing beans.xml" in a Seam project > ------------------------------------- > > Key: JBIDE-17827 > URL: https://issues.jboss.org/browse/JBIDE-17827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > In an imported Seam 2.3 project, there's a warning: > _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_ > Seam projects don't need a beans.xml file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17827: ----------------------------------- Fix Version/s: 4.2.0.CR1 > "Missing beans.xml" in a Seam project > ------------------------------------- > > Key: JBIDE-17827 > URL: https://issues.jboss.org/browse/JBIDE-17827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > In an imported Seam 2.3 project, there's a warning: > _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_ > Seam projects don't need a beans.xml file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17827: ---------------------------------------- Looks like that example project depends on cdi jars (so these jars are included in the project class path), if so then JBT maven adapters detect it and enable CDI support for the project. As workaround you can disable (set to Ignore) this validation warning using the Quick Fix on the validation warning. I'm not sure we can suggest any better solution. [~maxandersen], maybe it's better to set this validation problem to "Ignore" by default at all? WDYT? > "Missing beans.xml" in a Seam project > ------------------------------------- > > Key: JBIDE-17827 > URL: https://issues.jboss.org/browse/JBIDE-17827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Fix For: 4.2.0.CR1 > > > In an imported Seam 2.3 project, there's a warning: > _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_ > Seam projects don't need a beans.xml file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Steps to Reproduce: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. Result: There is the error that there are uncommitted changes and it is required to commit them first. !import-failed-uncommitted-changes.png! Expected Result: I should get warned about the inability to merge into my existing project (because of uncommitted changes) when I select the existing project, not only when the import is processed. was: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. EXPECTED RESULT: Question shell is shown or wizard is completed successfully and application on OpenShift is that one from the workspace (merged successfully). RESULT: There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). !import-failed-uncommitted-changes.png! Workaround via manually creating server adapter and pushing unfortunately wont work either: the existing project in the workspace does not have the openshift settings and wont be recognized as valid workspace for the server adapter: !cannot-create-server-adapter.png! > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Labels: application_wizard respin-a (was: respin-a) > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Description: (was: 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!) > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, push-force.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Steps to Reproduce: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. *Result:* There is the error that there are uncommitted changes and it is required to commit them first. !import-failed-uncommitted-changes.png! *Expected Result:* I should get warned about the inability to merge into my existing project (because of uncommitted changes) when I select the existing project, not only when the import is processed. was: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. Result: There is the error that there are uncommitted changes and it is required to commit them first. !import-failed-uncommitted-changes.png! Expected Result: I should get warned about the inability to merge into my existing project (because of uncommitted changes) when I select the existing project, not only when the import is processed. > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, push-force.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Attachment: (was: import.png) > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > 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, push-force.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014