Release notes for JBoss-IDE 1.2.1
Content
Introduction
This is a maintenance release. It's supposed to be installed and updated via the Eclipse Install/Update Manager. See Installation Notes.
System Requirements
- Eclipse 2.1.1 or greater.
- Version 1.3 or 1.4 of the Java 2 Runtime Environment. A JDK is needed for running JBoss 3.x.x inside Eclipse.
Installation Notes
Eclipse Install/Update Manager
- Start Eclipse.
- Select the Install/Update Perspective via Help > Software Updates > Update Manager or Window
> Open Perspective > Install/Update
- Select New > Site Bookmark from the context menu of the Feature
Update view. In the dialog fill the name with an unused one and the URL with http://jboss.sourceforge.net/jbosside/updates
- When you open the newly created node there is a child node called JBoss-IDE 1.0. By opening this child node you get nodes for all versions of JBoss-IDE
belonging to this category. Select the version you want to install and some information about this version is shown in the Preview
view. If this version or a higher one is not already installed the Preview view offers you an Install
button which you have to click if you want to install this version.
Tips :
- If you are behind a proxy you have to go to Window > Preferences > Install/Update,
select Enable HTTP Proxy connection and insert values for Host Address and Port.
- You can let Eclipse check if new updates of JBoss-IDE are available by selecting Help >
Software Updates > New Updates. Via Window > Preferences > Install/Update you can choose for which
changes of versions Eclipse is supposed to look.
- Have a look at the Eclipse documentation to get more information about the Install/Update Manager.
Manual Installation
- Download
org.jboss.ide.eclipse_1.2.1.bin.dist.zip
from Sourceforge site.
- Unzip the file to the home directory of Eclipse.
New Features
- No new features as it is a maintenance release
- Some experimental functionnalities have been disabled mainly because of
use of Eclipse internal API. As these features use internal API, future
version can break them.
Fixed Bugs
- Bug #794462 : can't set default server
- Bug #808728 : Packaging Plugin get confused with multi-project
- Bug #812911 : NullPointerException when adding a Doclet
- Bug #815214 : -classpath option doesn't work
- Patch #798557 : Fix for JDK 1.3.1 support
- Patch #798560 : JBoss IDE Exception reporting fix
Known Problems
- JBoss-IDE has not been tested on Eclipse 3.0M3. As it is a non final
release, API changes can still occurs. They will be taken into account later.
Currently, users must be aware that the Launcher plugin is broken is used
under Eclipse 3.0M3 as many API have changes in the debug layer of Eclipse.
Deployer Plugin
JBoss-IDE a two different type of target for deployement : File System and
Main Deployer. Here are some notes about the last one :
- The Main Deployer deployment target is based on the JMX Console Web
Application bundled with the JBoss Server. When using this kind of target,
you have to be sure that the JMX Console is deployed inside a running JBoss
instance. The deployement target sends HTTP requests to the JMX Console, in
order to control the Main Deployer MBean.
- As the JBoss 3.x.x series are not consitant, there are some differences
between the JMX Console bundled with JBoss 3.0.x and a JMX Console bundled
with JBoss 3.2.x. In the case of the Main Deployer deployment target, the
difference is in the HTTP query string used. Here is the query for JBoss
3.0.x series:
/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName={0}&argType=java.net.URL&arg=
XDoclet Modules
- JBoss-IDE look for the XDoclet modules in the directory
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.0/
. You can add or remove
modules from this directory as you like. After such a change you have to refresh the XDoclet module list and data.
When the XDoclet code assist is
used the first time after Eclipse has been restarted it looks for the cache and if the cache is there it just takes a couple of seconds to load the data. Go
to Window > Preferences > JBoss-IDE > XDoclet for refreshing module list and to Window
> Preferences > JBoss-IDE > XDoclet > Assist to force the data cache to be
regenerated.
JBoss-IDE file structure
JBoss-IDE 1.2.1 adds following directories to Eclipse.
ECLIPSE_HOME/features/org.jboss.ide.eclipse_1.2.1
ECLIPSE_HOME/plugins/org.apache.xalan_2.4.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.core_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.deployer.core_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.deployer.ui_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.launcher.core_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.launcher.ui_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.packaging.core_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.packaging.ui_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.ui_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.xdoclet.assist_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.xdoclet.run_1.2.1
ECLIPSE_HOME/plugins/org.jboss.ide.eclipse.xdoclet.ui_1.2.1
Disabling
You can disable JBoss-IDE by choosing the installed version in the Install/Update Manager via the Install Configuration
view then selecting the Disable button in the Preview
view. The JBoss-IDE files
don't get removed from disk via this mechanism and you can easily enable JBoss-IDE
again.
Uninstalling
- Delete all directories listes in the section file structure.
- You will need to restart Eclipse for the changes to take effect
Building from source
See the built-howto for
JBoss-IDE.