July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3100) JBDS 8 splash screen should be improved

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3100?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3100: -------------------------------- Assignee: Max Rydahl Andersen > JBDS 8 splash screen should be improved > --------------------------------------- > > Key: JBDS-3100 > URL: https://issues.jboss.org/browse/JBDS-3100 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: ui/branding > Affects Versions: 8.0.0.Beta3 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: uxtest > > There was a usability testing yesterday focused on OpenShift plugin. One note talked about splash screen: > {quote} > The 8 for JBDS spash screen looks a lot like Oracle 8 when that came out - big red 8. Probably need to do something different for the branding. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3103) Provide more info during OpenShift application creation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3103?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3103: ------------------------------------- Screenshot was probably taken later than should be. After acceptance of SSH host key there is a git clone showing percentage progress. Probably you mean first phase of applicaton creation, when IDE (and RHC too) sometimes seems to be "inactive" for few minutes - user don't know what is happening, bcs. there is no additional information (log). At first I was not sure so I have checked creation of a new applicaiton via RHC. RHC does not provide any information while an application is created. I am not sure, whether there is some log info at all. [~adietish] is there any obtainable information we could show to users while an application is created? > Provide more info during OpenShift application creation > ------------------------------------------------------- > > Key: JBDS-3103 > URL: https://issues.jboss.org/browse/JBDS-3103 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > During the project setup on OpenShift from the create new application wizard, the user is not provided much information about what is happening. This process does take a little while, and users would be more comfortable if they could see into what is happening for a better idea of if the process is failing or still working. A "more info" dropdown could be used on the modal to show log file information during this process. > https://www.evernote.com/shard/s230/sh/a750beed-4fc9-43d0-90a6-495573f09a... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3108) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3108?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3108: -------------------------------- Component/s: openshift > Add ability to "always accept" the hostkey of the SSH connection for cloning git repos > -------------------------------------------------------------------------------------- > > Key: JBDS-3108 > URL: https://issues.jboss.org/browse/JBDS-3108 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Labels: uxtest > > Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17176) Unable to browse and select PortletBridge runtime liberaries in JPP 6

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17176?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17176: ------------------------------------ Release Notes Text: For Red Hat JBoss Portal 6, the Dynamic Web Project wizard fails to detect the JBoss Portal PortletBridge .jar files when JSF Portletbridge Runtime Provider is selected in the JBoss JSF Portlet Capabilities step. Consequently, the .jar files cannot be selected and associated with the project from within the wizard. To work around this issue, follow the instructions here: 1. In the JBoss JSF Portlet Capabilities step of the Dynamic Web Project wizard, select Disable Library Configuration and complete any remaining steps of the wizard. 2. In the Project Explorer view, right-click the project and click Build Path→Configure Build Path. 3. In the Java Build Path pane, select the Libraries tab and click Add External JARs. 4. Navigate to /path/to/jboss-portal-6.x/modules/system/layers/gatein/org/jboss/portletbridge/ and select the portletbridge-api-3.3.1.Final-redhat-1.jar and portletbridge-impl-3.3.1.Final-redhat-1.jar. 5. Click OK to close the project Properties window. was: For Red Hat JBoss Portal 6, the Dynamic Web Project wizard fails to detect the JBoss Portal PortletBridge .jar files when JSF Portletbridge Runtime Provider is selected in the JBoss JSF Portlet Capabilities step. Consequently, the .jar files cannot be selected and associated with the project from within the wizard. To work around this issue, follow the instructions here: # In the JBoss JSF Portlet Capabilities step of the Dynamic Web Project wizard, select Disable Library Configuration and complete any remaining steps of the wizard. # In the Project Explorer view, right-click the project and click Build Path→Configure Build Path. # In the Java Build Path pane, select the Libraries tab and click Add External JARs. # Navigate to /path/to/jboss-portal-6.x/modules/system/layers/gatein/org/jboss/portletbridge/ and select the portletbridge-api-3.3.1.Final-redhat-1.jar and portletbridge-impl-3.3.1.Final-redhat-1.jar. # Click OK to close the project Properties window. > Unable to browse and select PortletBridge runtime liberaries in JPP 6 > --------------------------------------------------------------------- > > Key: JBIDE-17176 > URL: https://issues.jboss.org/browse/JBIDE-17176 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.Final > Reporter: abhishek vijra > Assignee: Snjezana Peco > Fix For: 4.2.x > > > For Jboss Portal Platform . If one uses Jboss Tools to built portlet application . In Jboss Tools portlet wizard it is impossible to select the PortletBridge Runtime Liberaries -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17176) Unable to browse and select PortletBridge runtime liberaries in JPP 6

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17176?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17176: ------------------------------------ Release Notes Text: For Red Hat JBoss Portal 6, the Dynamic Web Project wizard fails to detect the JBoss Portal PortletBridge .jar files when JSF Portletbridge Runtime Provider is selected in the JBoss JSF Portlet Capabilities step. Consequently, the .jar files cannot be selected and associated with the project from within the wizard. To work around this issue, follow the instructions here: # In the JBoss JSF Portlet Capabilities step of the Dynamic Web Project wizard, select Disable Library Configuration and complete any remaining steps of the wizard. # In the Project Explorer view, right-click the project and click Build Path→Configure Build Path. # In the Java Build Path pane, select the Libraries tab and click Add External JARs. # Navigate to /path/to/jboss-portal-6.x/modules/system/layers/gatein/org/jboss/portletbridge/ and select the portletbridge-api-3.3.1.Final-redhat-1.jar and portletbridge-impl-3.3.1.Final-redhat-1.jar. # Click OK to close the project Properties window. Affects: Release Notes > Unable to browse and select PortletBridge runtime liberaries in JPP 6 > --------------------------------------------------------------------- > > Key: JBIDE-17176 > URL: https://issues.jboss.org/browse/JBIDE-17176 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.Final > Reporter: abhishek vijra > Assignee: Snjezana Peco > Fix For: 4.2.x > > > For Jboss Portal Platform . If one uses Jboss Tools to built portlet application . In Jboss Tools portlet wizard it is impossible to select the PortletBridge Runtime Liberaries -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3069) Ungraceful shutdown results in multiple errors on startup

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-3069?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-3069: ---------------------------------- Release Notes Text: Restarting a virtual machine in which JBoss Developer Studio was running at the time of the virtual machine suspension results in JBoss Developer Studio immediately terminating with errors logged in the output. This may also be followed with error prompts when subsequently restarting JBoss Developer Studio with the same workspace. To work around this issue, to avoid terminating errors ensure you close JBoss Developer Studio prior to suspending the virtual machine. When this is not possible, to workaround workspace error prompts start JBoss Developer Studio with a different workspace and then change to the original workspace by clicking File→Switch Workspace. Affects: Release Notes > Ungraceful shutdown results in multiple errors on startup > --------------------------------------------------------- > > Key: JBDS-3069 > URL: https://issues.jboss.org/browse/JBDS-3069 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: runtime, upstream > Affects Versions: 7.1.1.GA > Reporter: Mustafa Musaji > Assignee: Snjezana Peco > Labels: needs_investigation > Fix For: 8.0.x > > Attachments: jbosstools-diagnostics-20140602154447.zip > > > During testing with Virtual Machines, if the machine is shutdown/stopped without closing JBDS, on restart JBDS doesn't start and we get a lot of errors (see attached). > Some of these are JBoss Tools errors and other Eclipse errors. Is there anything we can do on JBoss Tools or raise this with Eclipse developers upstream to look at? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3069) Ungraceful shutdown results in multiple errors on startup

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-3069?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-3069: ---------------------------------- Release Notes Text: Restarting a virtual machine in which JBoss Developer Studio was running at the time of the virtual machine suspension results in JBoss Developer Studio immediately terminating with errors logged in the output. This may also be followed with error prompts when subsequently restarting JBoss Developer Studio with the same workspace. To work around this issue, to avoid terminating errors ensure you close JBoss Developer Studio prior to suspending the virtual machine. When this is not possible, to workaround workspace error prompts start JBoss Developer Studio with a different workspace and then change to the original workspace by clicking File > Switch Workspace. (was: Restarting a virtual machine in which JBoss Developer Studio was running at the time of the virtual machine suspension results in JBoss Developer Studio immediately terminating with errors logged in the output. This may also be followed with error prompts when subsequently restarting JBoss Developer Studio with the same workspace. To work around this issue, to avoid terminating errors ensure you close JBoss Developer Studio prior to suspending the virtual machine. When this is not possible, to workaround workspace error prompts start JBoss Developer Studio with a different workspace and then change to the original workspace by clicking File→Switch Workspace.) > Ungraceful shutdown results in multiple errors on startup > --------------------------------------------------------- > > Key: JBDS-3069 > URL: https://issues.jboss.org/browse/JBDS-3069 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: runtime, upstream > Affects Versions: 7.1.1.GA > Reporter: Mustafa Musaji > Assignee: Snjezana Peco > Labels: needs_investigation > Fix For: 8.0.x > > Attachments: jbosstools-diagnostics-20140602154447.zip > > > During testing with Virtual Machines, if the machine is shutdown/stopped without closing JBDS, on restart JBDS doesn't start and we get a lot of errors (see attached). > Some of these are JBoss Tools errors and other Eclipse errors. Is there anything we can do on JBoss Tools or raise this with Eclipse developers upstream to look at? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16653) Forge integration should be able to take proxy info from eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16653?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-16653. ------------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-14375 > Forge integration should be able to take proxy info from eclipse > ---------------------------------------------------------------- > > Key: JBIDE-16653 > URL: https://issues.jboss.org/browse/JBIDE-16653 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16653) Forge integration should be able to take proxy info from eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16653?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-16653. ----------------------------------- > Forge integration should be able to take proxy info from eclipse > ---------------------------------------------------------------- > > Key: JBIDE-16653 > URL: https://issues.jboss.org/browse/JBIDE-16653 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17268) Forge wizards block eclipse UI while executing - need to be stoppable/canceble

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17268?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-17268. ------------------------------------- Resolution: Done Fixed in master > Forge wizards block eclipse UI while executing - need to be stoppable/canceble > ------------------------------------------------------------------------------ > > Key: JBIDE-17268 > URL: https://issues.jboss.org/browse/JBIDE-17268 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > > Forge wizards currently can block the eclipse UI. Run any non-trivial command and the Eclipse interface will be completely blocked until the forge command is cancelled, which may not be possible if the command is not using a fine-grained progress monitor and checks frequently. > Introducing a threaded command execution would allow the use of {code}commandThread.interrupt(){code} > And should allow both backgrounding of running wizards, but also more reliable cancellation with Forge's proxy support for thread interrupt handling. > Alternative is to: > provide method to cancel progress. > on first try cancel if command is "CanCancel" then use progress monitor cancel, if not use thread.interrupt() that will stop the progress on proxy boundaries. -- 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