[JBoss JIRA] (JBIDE-14571) Conflicting handlers after installing Eclipse VJET
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14571?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14571:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.0.Beta2)
> Conflicting handlers after installing Eclipse VJET
> --------------------------------------------------
>
> Key: JBIDE-14571
> URL: https://issues.jboss.org/browse/JBIDE-14571
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Victor Rubezhny
> Fix For: 4.2.x
>
>
> Error log:
> {code}
> Error
> Wed May 22 10:36:37 CEST 2013
> Conflicting handlers for org.eclipse.vjet.eclipse.debug.ui.launchShortcut.run: {org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@6c111d} vs {org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@d7a2d4}
> {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, 10 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-11602:
-----------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Beta2)
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.0.CR1
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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, 10 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-14708.
------------------------------------
Resolution: Done
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML 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, 10 months
[JBoss JIRA] (JBIDE-14624) Seam 2 project deployed to EAP 5.1 is not running
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14624?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-14624.
------------------------------------
Resolution: Done
Fixed in RC3.
> Seam 2 project deployed to EAP 5.1 is not running
> -------------------------------------------------
>
> Key: JBIDE-14624
> URL: https://issues.jboss.org/browse/JBIDE-14624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206
> JBoss EAP 5.1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> 1. Generate seam project for EAP5.1 runtime and Seam included in this EAP
> 2. Run it on EAP5.1 server
> ERROR:
> {noformat}
> 11:43:14,215 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/ state=PreParse mode=Manual requiredState=Parse
> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
> at org.jboss.Main.boot(Main.java:221)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
> at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
> ... 33 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
> at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
> ... 42 more
> {noformat}
> Looks like incorrect namespaces are used in web.xml file:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:web="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
> When web.xml file is opened in editor via double click it's not opened in web.xml editor. It has only source displayed. There is no Tree tab.
> When replaced with definition from web.xml file generated by JBDS 6.0.0 Everything works as expected:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
--
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, 10 months
[JBoss JIRA] (JBIDE-13725) Keep HTML5 jQuery Mobile Page Template up to date
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13725?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13725:
-----------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Beta2)
> Keep HTML5 jQuery Mobile Page Template up to date
> -------------------------------------------------
>
> Key: JBIDE-13725
> URL: https://issues.jboss.org/browse/JBIDE-13725
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.CR1
>
>
> Current jQuery Mobile js/css which is used by HTML5 jQuery Mobile Page Template is 1.3.0 (+ jQuery 1.9.1). We have to make sure that the final version of JBT 4.1.0 will have the latest jQuery Mobile links in this template.
> So far it's JQM 1.3.0 but it may change by the time of GA release.
--
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, 10 months
[JBoss JIRA] (JBIDE-14591) Properties Tab for jQuery/jQuery Mobile "widgets"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14591?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14591:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.0.Beta2)
> Properties Tab for jQuery/jQuery Mobile "widgets"
> -------------------------------------------------
>
> Key: JBIDE-14591
> URL: https://issues.jboss.org/browse/JBIDE-14591
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: 2013-05-22_1333.png
>
>
> The Properties Tab currently only has a General category. I would like to see us have another category where we have identified the most used jQuery/jQuery mobile widget properties such as:
> id (always at the top)
> data-role
> data-icon
> data-iconpos
> other data-* set of properties
> value (for input fields, value is pretty important)
> type (for input fields, critical)
> placeholder
> The available properties can be more extensive than what was originally shown in the wizard/dialog when the widget was dragged from the palette. Any property deemed important enough to show in the wizard/dialog should also be promoted into this new category.
> My proposal for the category name: jQuery
--
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, 10 months
[JBoss JIRA] (JBIDE-14854) Compilation errors in org.jboss.tools.vpe.browsersim
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-14854:
--------------------------------------
Summary: Compilation errors in org.jboss.tools.vpe.browsersim
Key: JBIDE-14854
URL: https://issues.jboss.org/browse/JBIDE-14854
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 4.1.0.Beta2
Reporter: Alexey Kazakov
Priority: Blocker
Fix For: 4.1.0.Beta2
{code}
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.vpe.browsersim: Compilation failure: Compilation failure:
[ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferencesStorage.java:[36,0]
[ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The public type BrowserSimSpecificPreferencesStorage must be defined in its own file
[ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowserSimSpecificPreferencesStorage.java:[36,0]
[ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The type BrowserSimSpecificPreferencesStorage is already defined
[ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferences.java:[18,0]
[ERROR] public class BrowserSimSpecificPreferences extends SpecificPreferences{
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The type BrowserSimSpecificPreferences is already defined
[ERROR] 3 problems (3 errors)
[ERROR] -> [Help 1]
{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, 10 months
[JBoss JIRA] (TOOLSDOC-338) Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-338?page=com.atlassian.jira.plug... ]
Alexey Kazakov edited comment on TOOLSDOC-338 at 6/12/13 7:33 PM:
------------------------------------------------------------------
{quote}
There are a number of perspectives available in the IDE. When the IDE starts, the default perspective is used as the
current perspective. If you use the tabs, menus or toolbars of the JBoss perspective frequently, you may want to make it
the default perspective.
{quote}
It seams that the default perspective is used only for the first start after installation/switching to a new workspace. Otherwise the last used perspective is used regardless what perspective is default.
And BTW if you switch to a new clean workspace then you will get default preferences so this preference (default perspective) is not very useful for users.
was (Author: akazakov):
{quote}
There are a number of perspectives available in the IDE. When the IDE starts, the default perspective is used as the
current perspective. If you use the tabs, menus or toolbars of the JBoss perspective frequently, you may want to make it
the default perspective.
{quote}
It seams that the default perspective is used only for the first start after installation/switching to a new workspace. Otherwise the last used perspective is used regardless what perspective is default.
> Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0.
> ------------------------------------------------------------------------------
>
> Key: TOOLSDOC-338
> URL: https://issues.jboss.org/browse/TOOLSDOC-338
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.0
>
> Attachments: UserGuide_Central.pdf
>
>
> Please review the content of the JBoss Central/JBoss Perspective chapter from a technical viewpoint:
> 1) Are features correctly documented?
> 2) Are there any features that are missing?
> Screenshots are currently missing and will be added closer to GA.
> For ease of tracking by docs, please give feedback as comments in this JIRA.
> The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content.
> Alternatively, the complete user guide to date is also available form:
> http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...
> https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile)
--
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, 10 months