March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19521) Connection wizard: should show authentication form as soon as server type is selected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19521?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19521: ------------------------------------- Description: # ASSERT: make sure you have only v3 plugins installed (only v3 OpenShift has no default server so that the wizard comes up with an empty server url) # EXEC: launch connection wizard (in Explorer, hit "New Connection") # ASSERT: wizard comes up with "OpenShift v3" preselected in Server Type # ASSERT: wizard comes up with empty Server url Result: No authentication form is show, the pane is empty Expected result: We should have the authentication form for OpenShift v3 and be able to provide credentials. > Connection wizard: should show authentication form as soon as server type is selected > ------------------------------------------------------------------------------------- > > Key: JBIDE-19521 > URL: https://issues.jboss.org/browse/JBIDE-19521 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > # ASSERT: make sure you have only v3 plugins installed (only v3 OpenShift has no default server so that the wizard comes up with an empty server url) > # EXEC: launch connection wizard (in Explorer, hit "New Connection") > # ASSERT: wizard comes up with "OpenShift v3" preselected in Server Type > # ASSERT: wizard comes up with empty Server url > Result: > No authentication form is show, the pane is empty > Expected result: > We should have the authentication form for OpenShift v3 and be able to provide credentials. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19534: ---------------------------------------- Summary: fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui Key: JBIDE-19534 URL: https://issues.jboss.org/browse/JBIDE-19534 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: {code} Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages {code} These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19533) Missing schemas for WildFly configuration

by Harald Wellmann (JIRA)

Harald Wellmann created JBIDE-19533: --------------------------------------- Summary: Missing schemas for WildFly configuration Key: JBIDE-19533 URL: https://issues.jboss.org/browse/JBIDE-19533 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.2.Final Reporter: Harald Wellmann The plugin specified entries in the Eclipse XML catalog are missing entries for the following namespaces used by WildFly 8.2.0.Final configuration files: * urn:jboss:domain:2.2 * urn:jboss:domain:undertow:1.2 As a result, XML validation in Eclipse fails. Workaround: Add user-defined catalog entries manually. (Note: WildFly 9.0.0.Beta1 has further schema updates - I'm not sure if these are supposed to be covered by the stable release line of JBoss Tools.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19528) Requirements Description column in Example Project Wizard cuts relevant part of text

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19528?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19528. --------------------------------- Resolution: Done "This project example requires" has been replaced by "requires". For the few cases where the requirements is still too long, a tooltip appears if you hover over them, or you can drag the column separators to the right. > Requirements Description column in Example Project Wizard cuts relevant part of text > ------------------------------------------------------------------------------------ > > Key: JBIDE-19528 > URL: https://issues.jboss.org/browse/JBIDE-19528 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Fred Bricon > Priority: Minor > Labels: usability > Fix For: 4.3.0.Alpha2 > > Attachments: New Project Example _099.png > > > First part of description "This project example requires" is always visible, but actual requirements name is cut. > !New Project Example _099.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19528) Requirements Description column in Example Project Wizard cuts relevant part of text

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19528?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19528: -------------------------------- Fix Version/s: 4.3.0.Alpha2 > Requirements Description column in Example Project Wizard cuts relevant part of text > ------------------------------------------------------------------------------------ > > Key: JBIDE-19528 > URL: https://issues.jboss.org/browse/JBIDE-19528 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Fred Bricon > Priority: Minor > Labels: usability > Fix For: 4.3.0.Alpha2 > > Attachments: New Project Example _099.png > > > First part of description "This project example requires" is always visible, but actual requirements name is cut. > !New Project Example _099.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19528) Requirements Description column in Example Project Wizard cuts relevant part of text

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19528?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19528: ----------------------------------- Assignee: Fred Bricon > Requirements Description column in Example Project Wizard cuts relevant part of text > ------------------------------------------------------------------------------------ > > Key: JBIDE-19528 > URL: https://issues.jboss.org/browse/JBIDE-19528 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Fred Bricon > Priority: Minor > Labels: usability > Attachments: New Project Example _099.png > > > First part of description "This project example requires" is always visible, but actual requirements name is cut. > !New Project Example _099.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19532: ---------------------------------- Attachment: Edit Server Runtime Environment _102.png > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Attachments: Edit Server Runtime Environment _102.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19532: ------------------------------------- Summary: "Edit Server Runtime Environment" Dialog configuration validation is broken Key: JBIDE-19532 URL: https://issues.jboss.org/browse/JBIDE-19532 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.3.CR1 Reporter: Denis Golovin Attachments: Edit Server Runtime Environment _102.png If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19531) Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19531?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19531: --------------------------------------- Linking duplicated issue, but it is not fixed. > Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19531 > URL: https://issues.jboss.org/browse/JBIDE-19531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > > See Steps to replicate. It doesn't report any errors about forge start. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19531) Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19531: ------------------------------------- Summary: Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors Key: JBIDE-19531 URL: https://issues.jboss.org/browse/JBIDE-19531 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.3.CR1 Reporter: Denis Golovin See Steps to replicate. It doesn't report any errors about forge start. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 March 2015