4. Issues
4.1. Resolved Issues
To view information about issues resolved in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following advanced search query as one line:
(project in (JBDS) AND affectedVersion < "8.0.0.Alpha1" AND fixVersion in ("8.0.0.Alpha1","8.0.0.Alpha2","8.0.0.Beta1","8.0.0.Beta2","8.0.0.Beta3","8.0.0.CR1","8.0.0.CR2","8.0.0.GA") AND fixVersion not in ("7.1.0.Beta1","7.1.0.CR1") OR project in (JBIDE) AND affectedVersion < "4.2.0.Alpha1" AND fixVersion in ("4.2.0.Alpha1","4.2.0.Alpha2","4.2.0.Beta1","4.2.0.Beta2","4.2.0.Beta3","4.2.0.CR1","4.2.0.CR2","4.2.0.Final") AND fixVersion not in ("4.1.0.CR1","4.1.1.Alpha1","4.1.1.Alpha2","4.1.1.Beta1","4.1.1.CR1","4.1.2.CR1")) AND type in (Bug) AND resolution in (Done)
The following customer-reported resolved issues are highlighted:
- JBDS-2921
- On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file. Drop events of type String were not recognized and consequently the drag-and-drop action for files did not work. This issue has been resolved by ensuring the IDE recognizes drop events of type String and dragging a file from Nautilus File Manager into an Editor view now successfully opens the file.
- JBIDE-14001
- On the first IDE and server restart or the first workspace and server restart after marking a new file as deployable, the file was no longer deployed. At the session restart, there was no check to ensure the deployed file IDs matched those in the previous session. This issue has been resolved by ensuring that the file is properly found during the next session and now marking a new file as deployable persists from one session to the next.
4.2. Known Issues
To view information about known issues in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following advanced search query as one line:
(project in (JBDS) AND affectedVersion >= "7.0.0.GA" AND affectedVersion <= "8.0.0.GA" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "8.0.0.GA") OR project in (JBIDE) AND affectedVersion >= "4.1.0.Final" AND affectedVersion <= "4.2.0.Final" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.2.0.Final")) AND type in (Bug)The query results correspond to reported issues but the issues may not yet have been confirmed by the product team.
The following customer-reported known issues are highlighted:
- JBDS-3069
- 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 →.
- JBDS-3119
- Certain xsd schemas appear to fail validation in Eclipse but deploy correctly. The workaround at the current time is to ignore these errors. The examples and archetypes available from JBoss Developer Studio still deploy.
- JBIDE-17176
- For Red Hat JBoss Portal 6, the Dynamic Web Project wizard fails to detect the JBoss Portal PortletBridge
.jarfiles when JSF Portletbridge Runtime Provider is selected in the JBoss JSF Portlet Capabilities step. Consequently, the.jarfiles 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 →.
- In the Java Build Path pane, select the Libraries tab and click .
- Navigate to
/path/to/jboss-portal-6.x/modules/system/layers/gatein/org/jboss/portletbridge/and select theportletbridge-api-3.3.1.Final-redhat-1.jarandportletbridge-impl-3.3.1.Final-redhat-1.jarfiles. - Click to close the project Properties window.
4.3. Operating System Variations and Issues
The following operating system variations and issues are highlighted:
- Microsoft Windows Operating Systems
- When using BrowserSim, the JavaFX browser option is not available for Microsoft Windows operating systems and therefore Chrome Dev Tools for debugging are also not available. To work around this restriction, you can install 32-bit Safari which contains the necessary library requirements for the SWT Browser option. If opting for this work around and using a 64-bit Microsoft Windows operating system running 64-bit version of JBoss Developer Studio, you must additionally set BrowserSim to use a 32-bit JVM by editing the BrowserSim preferences from within the IDE.
- You can install JBoss Developer Studio stand-alone or Eclipse to a shared location for use by multiple users. Post-installation, the system administrator must set the installation directory to read-only for all standard users to ensure that users are only prompted to create workspaces in their own user space.
- Hybrid Mobile Tools iOS features necessitate XCode which is only available for OS X and therefore these features are not available for Microsoft Windows operating systems.
- Linux-based Operating Systems
- General
- GTK is required as the windowing system for the IDE on Linux distributions but if using GTK3 you may experience IDE rendering issues. To work around any issues, before starting the IDE, on the command line enter
export SWT_GTK3=0
to disable GTK3 and revert to GTK2. - Hybrid Mobile Tools iOS features necessitate XCode which is only available for OS X and therefore these features are not available for Linux distributions.
- Red Hat Enterprise Linux
- When Oracle JDK is installed through the command line with
yum, you may find that only a subset of the complete JDK packages are installed. In particular, JavaFX may not be installed on your system and when trying to run BrowserSim with the JavaFx web engine you are prompted with IDE error messages. To ensure you have JavaFX installed, on the command line enteryum install java-<version>-oracle-javafx
where<version>matches the version of Oracle JDK you are using. Alternatively, download and install the complete JDK, which includes JavaFX, from the Oracle website. - On Red Hat Enterprise Linux 6 operating systems, only the GTK2 option is available for BrowserSim because the webkitgtk3 package is not distributed. Both SWT and JavaFX Browsers can still be used for BrowserSim giving full scope of the BrowserSim debug tools.
- On Red Hat Enterprise Linux 7 operating systems, the JavaFX Browser option is available only if choosing BrowserSim GTK option as GTK2 and the SWT Browser option is available only if choosing BrowserSim GTK option as GTK3.
- Fedora
- When using BrowserSim, the JavaFX Browser option is not available for Fedora operating systems and therefore Chrome Dev Tools for debugging are also not available. The SWT Browser option is still available.
- Ubuntu
- When using BrowserSim, the JavaFX Browser option is not available for Ubuntu operating systems and therefore Chrome Dev Tools for debugging are also not available. The SWT Browser option is still available.
