December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13723) Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13723?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13723: ------------------------------------- Estimated Difficulty: Medium > Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13723 > URL: https://issues.jboss.org/browse/JBIDE-13723 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Labels: application_wizard > Fix For: 4.2.x > > Attachments: out.ogv > > > OpenShift wizard shows an error dialog with "Could not import project to the workspace." message: > {code} > org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project ticket-monster has uncommitted changes. Please commit those changes first. > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ConfigureGitSharedProject.execute(ConfigureGitSharedProject.java:101) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizardModel.configureGitSharedProject(OpenShiftExpressApplicationWizardModel.java:158) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:319) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > Although git status says there nothing to commit: > {code} > [sbunciak@dhcp-27-195 ticket-monster]$ git status > # On branch master > nothing to commit (working directory clean) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16040) Embed wizard: Web balancer cartridge should not be listed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16040?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16040: ------------------------------------- Assignee: (was: Andre Dietisheim) > Embed wizard: Web balancer cartridge should not be listed > --------------------------------------------------------- > > Key: JBIDE-16040 > URL: https://issues.jboss.org/browse/JBIDE-16040 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: embed_wizard > Fix For: 4.2.x > > Attachments: haproxy_cartridge.png > > > There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed. > !haproxy_cartridge.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13663?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13663: ------------------------------------- Assignee: (was: Max Rydahl Andersen) > Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13663 > URL: https://issues.jboss.org/browse/JBIDE-13663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > Attachments: push-local-commit.png > > > usecase: > EXECUTE: Create openshift project > EXECUTE: Make sure all is committed and Pushed. > EXECUTE: Edit an existing committed file - commit it. > EXECUTE: Add a "xyz.log" file that is not to be committed. > EXECUTE: Publish to server. > ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. > EXECUTE: Wait for publish to finish. > ASSERT: "xyz.log" should *not* be pushed nor committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13663?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13663: ------------------------------------- Estimated Difficulty: Medium > Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13663 > URL: https://issues.jboss.org/browse/JBIDE-13663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > Attachments: push-local-commit.png > > > usecase: > EXECUTE: Create openshift project > EXECUTE: Make sure all is committed and Pushed. > EXECUTE: Edit an existing committed file - commit it. > EXECUTE: Add a "xyz.log" file that is not to be committed. > EXECUTE: Publish to server. > ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. > EXECUTE: Wait for publish to finish. > ASSERT: "xyz.log" should *not* be pushed nor committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13352) Should be able to remove cartridge with "Remove" in the context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13352: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) Assignee: (was: Andre Dietisheim) Estimated Difficulty: Medium > Should be able to remove cartridge with "Remove" in the context menu > -------------------------------------------------------------------- > > Key: JBIDE-13352 > URL: https://issues.jboss.org/browse/JBIDE-13352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: remove-embedded-cartridge.png > > > If you have a cartridge embedded to your application you'll see it listed as node below your application: > !remove-embedded-cartridge.png! > To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13352) Explorer: Should be able to remove cartridge with "Remove" in the context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13352: ------------------------------------- Summary: Explorer: Should be able to remove cartridge with "Remove" in the context menu (was: Should be able to remove cartridge with "Remove" in the context menu) > Explorer: Should be able to remove cartridge with "Remove" in the context menu > ------------------------------------------------------------------------------ > > Key: JBIDE-13352 > URL: https://issues.jboss.org/browse/JBIDE-13352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: remove-embedded-cartridge.png > > > If you have a cartridge embedded to your application you'll see it listed as node below your application: > !remove-embedded-cartridge.png! > To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13352) Explorer: Should be able to remove cartridge with "Remove" in the context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13352: ------------------------------------- Labels: explorer (was: ) > Explorer: Should be able to remove cartridge with "Remove" in the context menu > ------------------------------------------------------------------------------ > > Key: JBIDE-13352 > URL: https://issues.jboss.org/browse/JBIDE-13352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: LATER > > Attachments: remove-embedded-cartridge.png > > > If you have a cartridge embedded to your application you'll see it listed as node below your application: > !remove-embedded-cartridge.png! > To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13384: ------------------------------------- Assignee: (was: Rob Stryker) > Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13384 > URL: https://issues.jboss.org/browse/JBIDE-13384 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.2.Final > Reporter: Stefan Bunciak > Priority: Minor > Fix For: 4.2.x > > > This issue should find solution to this situation: > * create application on openshift, then binary deployed another app to it > * delete the server adapter > * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically? > Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13384: ------------------------------------- Estimated Difficulty: Medium > Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13384 > URL: https://issues.jboss.org/browse/JBIDE-13384 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.2.Final > Reporter: Stefan Bunciak > Priority: Minor > Fix For: 4.2.x > > > This issue should find solution to this situation: > * create application on openshift, then binary deployed another app to it > * delete the server adapter > * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically? > Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13384: ------------------------------------- Labels: server_adapter_wizard (was: ) > Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13384 > URL: https://issues.jboss.org/browse/JBIDE-13384 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.2.Final > Reporter: Stefan Bunciak > Priority: Minor > Labels: server_adapter_wizard > Fix For: 4.2.x > > > This issue should find solution to this situation: > * create application on openshift, then binary deployed another app to it > * delete the server adapter > * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically? > Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 December 2013