[JBoss JIRA] (JBIDE-14828) OpenShift application/import wizard: if git clone directory already exist i cannot do anything
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14828?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14828:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> OpenShift application/import wizard: if git clone directory already exist i cannot do anything
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-14828
> URL: https://issues.jboss.org/browse/JBIDE-14828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: application-folder-already-exists.png
>
>
> steps to reproduce:
> # EXEC: create and/or import some appliaction from OpenShift to your local workspace using the application/import wizard
> # EXEC: once you have the project imported to your workspace, delete it
> # EXEC: once it is deleted, go and try to re-import the very same application
> Result:
> The 3rd wizard page errors on the git cloning destination. You're told that the destination folder already exists within the clone destination folder. The only way out currently is to choose a different clone destination folder.
> !application-folder-already-exists.png!
> Expected:
> It would help a lot if wizard would allow you to overwrite the existing destination. The wizard could also check if the given folder holds a prior clone and then allow one to "reuse" this folder. The given folder would then simply get imported to Eclipse and we'd fetch instead of cloning.
--
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, 4 months
[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails
by Steven Hawkins (JIRA)
Steven Hawkins created JBIDE-16133:
--------------------------------------
Summary: No indication that management authentication fails
Key: JBIDE-16133
URL: https://issues.jboss.org/browse/JBIDE-16133
Project: Tools (JBoss Tools)
Issue Type: Quality Risk
Components: server
Reporter: Steven Hawkins
Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
On server startup without any indication of what it means.
--
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, 4 months
[JBoss JIRA] (JBIDE-16019) Reorganize JST component
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16019?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-16019:
-----------------------------------------
It looks like the fix for VPE is incomplete:
{code}
[ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.vpe.cordovasim.eclipse 3.5.100.qualifier to bundle org.jboss.tools.jst.jsp 3.3.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.vpe.cordovasim.eclipse 3.5.100.qualifier to bundle org.jboss.tools.jst.jsp 3.3.0.; No solution found because the problem is unsatisfiable.]
{code}
> Reorganize JST component
> ------------------------
>
> Key: JBIDE-16019
> URL: https://issues.jboss.org/browse/JBIDE-16019
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
> Attachments: dependencies.gliffy, dependencies.png
>
>
> !dependencies.png!
> My suggestions:
> *1. Clean up (remove obsolete plugins):*
> * jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
> * jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
> * jst.web.tiles/tiles.ui.
> *2. Fix dependency problem between jsp/html editor and other jsp/html editor related UI features (such as html5 property view) by merging all UI plugins into jst.web.ui plug-in:*
> * jst.jsp (JSP/HTML editor, content assist, outline)
> * jst.web.ui (palette, wizards, ...)
> * jst.text.ext (Open Ons)
> * jst.css (css editor)
--
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, 4 months
[JBoss JIRA] (JBIDE-16130) Openshift Enterprise: Creating (separate) jenkins application invoked by adding jenkins client to other application does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16130?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16130:
-------------------------------------
Description: (was: Steps to reproduce:
ASSERT: Have OpenShift Enterprise connection
ASSERT: Don't have Jenkins application on the given connection
EXEC: Open wizard for new application
EXEC: Choose some application type (doesn't matter which one)
EXEC: Toggle checkbox next to jenkins cartridge
EXEC: Click on "Apply" button
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
!jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".)
Steps to Reproduce:
Steps to reproduce:
# ASSERT: Have OpenShift Enterprise connection
# ASSERT: Don't have Jenkins application on the given connection
# EXEC: Open wizard for new application
# EXEC: Choose some application type (doesn't matter which one)
# EXEC: Toggle checkbox next to jenkins cartridge
# EXEC: Click on "Apply" button
Result:
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
!jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
Workaround Description: Create a jenkins application in a first step. Then get over to create your application and embed jenkins client. You wont get prompted to create a jenkins application (since it already exists)
> Openshift Enterprise: Creating (separate) jenkins application invoked by adding jenkins client to other application does not work
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16130
> URL: https://issues.jboss.org/browse/JBIDE-16130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: jenkins.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, 4 months
[JBoss JIRA] (JBIDE-16127) OpenShift Explorer: Openshift icon for new connection should preselect new connection (not existing connection)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16127?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16127:
-------------------------------------
Summary: OpenShift Explorer: Openshift icon for new connection should preselect new connection (not existing connection) (was: Openshift icon for new connection should open new connection)
> OpenShift Explorer: Openshift icon for new connection should preselect new connection (not existing connection)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16127
> URL: https://issues.jboss.org/browse/JBIDE-16127
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> The "New connection icon" in OpenShift Explorer should open new connection in case, if there is any connection in OpenShift explorer presented and selected. It should have same functionality as "New connection" menu item in context menu of any selected connection. Now when you click on this icon, there is shown a shell with the given presented connection in ComboBox and filled password.
--
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, 4 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16129:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
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, 4 months
[JBoss JIRA] (JBIDE-16127) Openshift icon for new connection should open new connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16127?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16127:
-------------------------------------
Fix Version/s: 4.2.x
> Openshift icon for new connection should open new connection
> ------------------------------------------------------------
>
> Key: JBIDE-16127
> URL: https://issues.jboss.org/browse/JBIDE-16127
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> The "New connection icon" in OpenShift Explorer should open new connection in case, if there is any connection in OpenShift explorer presented and selected. It should have same functionality as "New connection" menu item in context menu of any selected connection. Now when you click on this icon, there is shown a shell with the given presented connection in ComboBox and filled password.
--
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, 4 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16129:
-------------------------------------
Summary: Environment Variables wizard: Refresh should warn that it'll undo all changes (was: Refresh in Edit environment variables shell should warn about undo operation)
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
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, 4 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16129:
-------------------------------------
Fix Version/s: 4.2.0.Alpha1
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
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, 4 months