[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-13987.
---------------------------------
Labels: new_and_noteworthy (was: )
Release Notes Text:
JBoss Central now displays wizards for plugins that may not have been installed yet. for instance, it will display the OpenShift Application link even if you don't have the JBoss OpenShift tooling installed. Clicking on that link will ask you to install the required OpenShift features.
Moreover that wizard list can be updated, reordered at anytime remotely from the JBoss Tools team.
As part of this change, the GWT Project wizard has been replaced by the Maven Project wizard.
Resolution: Done
Fixed with https://github.com/jbosstools/jbosstools-central/commit/697a558c2670d1863...
http://www.screencast.com/users/fbricon/folders/Jing/media/2d88687e-0c0f-...
> Improve project wizards in JBoss Central : Proxy Wizards
> --------------------------------------------------------
>
> Key: JBIDE-13987
> URL: https://issues.jboss.org/browse/JBIDE-13987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements :
> - wizard list (label/order/description) must be updateable remotely
> - show wizards (including the proper icon) even if their contributing plugins are missing
> - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins
> The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes :
> - id : the proxy wizard id
> - label : the proxy wizard label shown in JBoss Central
> - wizardId : the real wizard id used by Central to open the wizard dialog
> - iconPath : the path to the wizard icon (independent of required connector)
> - description : the description shown in Central when hovering over the wizard link
> - requiredConnectorIds : the connector ids to install if the real wizard is not available
> - priority : order in which the wizard is displayed in JBoss Central
> The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons.
> The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13551) Error in error log when starting server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13551?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13551:
-------------------------------------
Work is continuing on this issue over at: https://bugs.eclipse.org/bugs/show_bug.cgi?id=402073
BUg seems pretty deep and they're having trouble fixing it.
> Error in error log when starting server
> ---------------------------------------
>
> Key: JBIDE-13551
> URL: https://issues.jboss.org/browse/JBIDE-13551
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Alpha1
> Environment: JBoss Developer Studio Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> JBoss AS 7.1.1.Final
> JBoss EAP 5.1
> Reporter: Vlado Pakan
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.1.0.Final
>
>
> 1. Start server either JBoss AS 7.1.1.Final or JBoss EAP 5.1
> 2. Open error log
> ERROR: Error log contains error:
> Conflicting handlers for org.eclipse.debug.ui.commands.eof: {org.eclipse.debug.internal.ui.views.console.ProcessConsolePageParticipant$EOFHandler@138b3064} vs {org.eclipse.debug.internal.ui.views.console.ProcessConsolePageParticipant$EOFHandler@138b3064}
> An exception stack trace is not available.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-2050) Add support for ServiceBindingManager for port discovery. (Was AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2050?page=com.atlassian.jira.plugin... ]
Rob Stryker resolved JBIDE-2050.
--------------------------------
Resolution: Won't Fix
No changes will be made to earlier server adapters, and AS > 7 already has a solution in place for the port offsets. Sorry.
> Add support for ServiceBindingManager for port discovery. (Was AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-2050
> URL: https://issues.jboss.org/browse/JBIDE-2050
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 2.0.1
> Environment: Linux 2.6.22-14-generic, Eclipse Europa Version: 3.3.2, JbossToolsPlugin 2.0.1GA-ALL linux, JbossAS 4.2.2.GA
> Reporter: Mario Balaban
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: LATER
>
>
> On the same machine I had to create 2 instances of JbossAS, one for testing and another for development. The instance used for testing is using the "default" configuration. The test (default) instance I am able to start and to stop correctly from the Eclipse IDE. The "devel" instance that is a copy of the "default" configuration but has different port bindings (modified jboss-service.xml by uncommenting the tag <mbean code="org.jboss.services.binding.ServiceBindingManager"..../> ) has problems when starting and stopping from eclipse IDE. In the console window of IDE I see " [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:993ms" but the state of the server in the "Servers" window of the IDE is Starting... It remains "Starting..." till an OutOfMemory is visualized in the IDE. This error happens even when no applications are deployed to the deploy directory of the "devel" configuration. It seems that the problem is associated to different port bindings used by "devel" configuration.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-14349) Support for wildfly server type
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14349?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-14349:
--------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> Support for wildfly server type
> -------------------------------
>
> Key: JBIDE-14349
> URL: https://issues.jboss.org/browse/JBIDE-14349
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
>
> This task is currently a bit vague until we have a more clear direction, however, this will serve as a convenient wrapper bug for the implementation of a new wildfly server type.
> Much is not yet decided. All subtasks, concerns, and discussion should occur here or on the mailing lists.
--
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
13 years, 1 month