6:23 a.m.
Author: rob.stryker(a)jboss.com
Date: 2012-06-06 07:23:49 -0400 (Wed, 06 Jun 2012)
New Revision: 41740
Added:
trunk/documentation/whatsnew/as/as-news-3.3.0.CR1.html
trunk/documentation/whatsnew/jmx/jmx-news-1.2.0.CR1.html
Modified:
trunk/documentation/whatsnew/index.html
Log:
JBIDE-11938 to trunk
Added: trunk/documentation/whatsnew/as/as-news-3.3.0.CR1.html
===================================================================
--- trunk/documentation/whatsnew/as/as-news-3.3.0.CR1.html (rev
0)
+++ trunk/documentation/whatsnew/as/as-news-3.3.0.CR1.html 2012-06-06 11:23:49 UTC (rev
41740)
@@ -0,0 +1,246 @@
+<html>
+
+<head>
+<link rel="stylesheet" href="../whatsnew.css">
+<title>JBoss AS Tools 3.3.0.CR1 News</title>
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-17645367-5']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' :
'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+
+</script></head>
+
+<body>
+
+<h1>JBoss AS Tools 3.3.0.CR1 What's New</h1>
+
+ <p align="right"><a href="../index.html">< Main
Index</a> <a
+href="../openshift/openshift-news-2.3.0.CR1.html">OpenShift
Tools></a></p>
+<table border="0" cellpadding="10" cellspacing="0"
width="80%">
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Server</h3>
+ <hr/>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Server locations with space now work
properly!</b></p>
+ </td>
+ <td valign="top" width="90%">
+
+ <p>Servers that live in directories with spaces have long been a problem
issue in the past, but now, rest assured that your
+ servers will be well taken care of! Starting and stopping these servers should
now work flawlessly,
+ and with the correct arguments no doubt!! Various other server argument bugs
were fixed as well,
+ helping to make JBossTools as strong as our word! You're in good hands,
with JBossTools!</p>
+ <p><small>
+ <a href="https://issues.jboss.org/browse/JBIDE-12001">Primary
Jira</a></br>
+ Related Jiras: <a
href="https://issues.jboss.org/browse/JBIDE-11824">JBIDE-118...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-12041">JBIDE-120...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11853">JBIDE-118...
+ </small></p>
+ </td>
+ </tr>
+
+ <tr><td colspan="2"><hr /></td></tr>
+ <tr>
+ <td valign="top" align="right">
+ <p><b>JBoss AS7 can now expose your management port for local and
remote instances!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>With the addition of a new checkbox in the server editor, users can now
expose their management port when
+ starting and stopping remote (or local!) instances of the server. This ensures
that management commands,
+ such as starting and stopping the deployment scanner, or polling the server,
work.</p>
+ <p> But be careful! If your server is on production somewhere, it might be
unwise to leave that much awesome power
+ available to any computer with a jboss installation and an internet
connection! Ask your system administrator for guidance.
+ And never forget, the infinite is unknown at JBossTools!
+ </p>
+ <p><img
src="https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921...
alt="Expose Management Port screenshot"/></p>
+ <p><small>
+ <a
href="https://issues.jboss.org/browse/JBIDE-11921">Primary
Jira</a></br>
+ <a href="https://issues.jboss.org/browse/JBIDE-1">Related
Bug</a></br>
+ <a
href="https://issues.jboss.org/browse/JBIDE-11989">Related
Bug</a></br>
+
+ </small></p>
+
+ </td>
+ </tr>
+ <tr><td colspan="2"><hr /></td></tr>
+ <tr>
+ <td valign="top" align="right">
+ <p><b>AS7 JMX Connections strengthened!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>As mentioned over in <a
href="../jmx/jmx-news-1.2.0.CR1.html">JMX Tools</a>, support for AS
7's JMX connectivity
+ has moved forward a lot, allowing for faster and smoother usage. With
everything from minimizing the number of connections,
+ cleaning up stalled threads, and erroring in a more graceful fashion, it's
almost as if JBossTools and AS 7's JMX support
+ were made for each other! With JBossTools, if you're going, we'll fly
you there! And how!! </p>
+
+ <p><small>
+ Related Jiras: <a
href="https://issues.jboss.org/browse/JBIDE-11483">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11482">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11481">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11064">JBIDE-110...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11872">JBIDE-118...
+ </small></p>
+ </td>
+ </tr>
+ <tr><td colspan="2"><hr /></td></tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Lend me your EAR, and make it Runnable!!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>Take any EAR project, right-click it, run it on your server, and watch a
browser open. Why is this so cool? Because webtools doesn't have it!
+ That's right. Webtools can find some way to run all their projects on your
server, except for EAR projects that is!
+ Well not any more. The new behaviour in JBossTools is to select the first Web
project in your EAR and run that one instead.
+ The full module will get published, of course, but at least now a browser will
show up with something! </p>
+ <p>In a related issue, right-clicking a .java file to run on your server
seems to have always come up with a bit of a
+ strange choice for a web url. It'd actually open a URL like
yourwar.war/web-inf/classes/ReallyCoolThing.java.
+ No matter how cool that thing really is, I don't think that's a URL we
want loaded. Do you?
+ <p>So everybody, close the door, code your web store, and everybody dance
the dinosaur! You've lent me your ear, and this is your reward! </p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-10930">Primary
Jira</a><br/>
+<a href="https://issues.jboss.org/browse/JBIDE-11414">Related
Jira</a></small></p>
+ </td>
+ </tr>
+ <tr><td colspan="2"><hr /></td></tr>
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Server Editor's module restart pattern revised, and
FIXED!!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>You may remember the introduction of this feature in beta3, but what you
might not have noticed was that a
+ workspace restart was required if you ever intended to CHANGE that value. Talk
about a sticky property! Ugh!
+ A healthy dose of bug-be-gone has left this particular issue dead, but not
forgotten.... well, at least not by some.
+ You guys can forget it if you want. As Audrey Hepburn once said, Happiness is
health, and a short memory! </p>
+ <p><img
src="https://issues.jboss.org/secure/attachment/12351312/JBIDE-10464...
alt="module restart pattern"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-10733">Related
Jira</a></small></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>New fileset for your AS 7? Now with sensible
defaults!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>If you've tried to open your servers view and right-click the
"filesets" category, with the intention of adding
+ a new fileset, you may have noticed that AS 7's defaults were a little...
outdated. Default folders
+ that only make sense for AS 6 and below are soOoOOoo beta2. It's a bit
like seeing someone wear bellbottoms...
+ it doesn't ruin your day, but it does make you feel just a little more sad
about where the world is heading. Either way,
+ JBossTools 3.3.0 CR1 replaces those old rags with new sensible defaults. I
can't promise they'll make you smile,
+ but, lets all be honest with ourselves... they will ;) <small>JBossTools
Rules!!!</small></p>
+ <p><img src="images/11059.png" alt="new fileset
defaults"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-11059">Related
Jira</a></small></p>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <p><b>No IPs, no problem! IPv6 support verified!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>According to our devs and our QE teams, IPv6 support for JBossTools is
online and fully operational.
+ Loading local AS 7 servers with a hostname of "::1" will no longer
result in a stuck process
+ and an unresponsive and recalcitrant server refusing repeated requests to shut
down already!
+ Browser support in eclipse is also present, so Run-on-server actions should
yield the expected result.
+ It's times like this you know JBossTools was the right choice, at the
right time, and for the right reasons. </p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-11626">Related
Jira</a></small></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Stop polluting my deployments folder!</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>Back during older versions of JBoss AS, all deployments went into a
deploy folder.
+ This included deployments JBoss itself provided. Well, users didn't like
having to dig
+ through this mess to remember which deployments were theirs and which
weren't. They demanded
+ the ability to segregate their deployments out, and we gave it to
them!</p>
+ <p>While this isn't so much an issue now as it was then, there are
still a significant number
+ of users, especially in dev mode, who prefer to keep their deployments
somewhere other than
+ the app server's standard deployments folder. Well, Beta3 and CR1 have
both enhanced this
+ support for JBoss AS 7 in a variety of ways. First, all three standard
deployment options are now
+ enabled (server, metadata, and custom), as they are for previous versions. And
second, the running server will receive
+ the list of folders that need to be added (or removed) from the server's
deployment scanners. </p>
+ <p>No more will users have to suffer through widely differing levels of
functionality depending on
+ their app server version. The infinite is unknown at JBossTools.</p>
+
+ <p><img src="images/9239.png" alt="new fileset
defaults"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-9239">JBIDE-9239...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11297">JBIDE-112...
+ </small></p>
+ <p> In a related issue, some early adopters were confused when a scanner
they had added
+ had a 0-second interval, which basically meant inactive. We've added a
popup dialog
+ to alert the user in this case. If your server has inactive scanners,
you'll be provided a
+ chance to change it, or ignore that dialog forever. </p>
+ <p><img
src="https://issues.jboss.org/secure/attachment/12352599/JBIDE-11275...
alt="new fileset defaults"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-11275">JBIDE-112...
</small></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Which args do I modify again?</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>Some users who were running servers based on RSE were getting confused
how, exactly,
+ to change their launch and stop arguments. By opening the server view, and
double-clicking
+ your server, the server editor opens. If you then click "Open Launch
Configuration", you
+ have a huge array of options available, but, perhaps, too many options.
</p>
+ <p>To help clear up the confusion, if you're running an RSE server,
opening the launch
+ configuration will now ONLY show you the remote launch args tab. If you're
running
+ a local server, however, all options (minus the RSE tab) will show.
</p>
+ <p>A small step every day, with JBossTools leading the way!</p>
+ <p><img src="images/11587.png" alt="zero-second
scanner"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-11587">Related
Jira</a></small></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right">
+ <p><b>Default classpaths per server made more user
friendly</b></p>
+ </td>
+ <td valign="top" width="90%">
+ <p>A while ago, users were asking for ways to customize their project
classpaths
+ on a per-server basis. While developing it, we figured that most users
wouldn't
+ want to customize each and every server they make. If they happened to make 2
or 3
+ servers with different launch args, for example, it would be tedious to try to
+ update the classpath for each one manually. </p>
+ <p>Instead we went with the ability to customize it on a per server-type
basis, or,
+ to add some jars to a global list for all server types. This is accessible
through
+ window -> preferences -> server -> runtime environment
-> Default Classpaths.
+ Well, somehow during the
+ dev cycle, a lot of this proved to not work in all cases. It also was shown to
need
+ a real cleanup to make it more user friendly. The area most confusing to
users
+ was Adding a new fileset. And so we cleaned that up, added better defaults,
+ and removed fields that just didn't belong! </p>
+
+ <p>Remember, for all your development environment needs, JBossTools is
+ <a
href="http://www.youtube.com/watch?v=oHg5SJYRHA0">NEVER</... gonna give
you up!!!</p>
+ <p><img src="images/11820.png" alt="default classpath
entries"/></p>
+ <p><small><a
href="https://issues.jboss.org/browse/JBIDE-11820">Related
Jira</a></small></p>
+ </td>
+ </tr>
+
+
+
+
+
+</table>
+
+</body>
+
+</html>
+
+
Modified: trunk/documentation/whatsnew/index.html
===================================================================
--- trunk/documentation/whatsnew/index.html 2012-06-06 11:05:38 UTC (rev 41739)
+++ trunk/documentation/whatsnew/index.html 2012-06-06 11:23:49 UTC (rev 41740)
@@ -52,8 +52,11 @@
<td valign="top" align="left">
<p align="right"><b>3.3.0.CR1</b>
<td valign="top">
+
+ <p><a href="as/as-news-3.3.0.CR1.html">JBoss AS Server
Tools</a></p>
+ <p><a
href="jmx/jmx-news-1.2.0.CR1.html">JMX</a></p>
<p><a
href="maven/maven-news-3.3.0.CR1.html">Maven</a></p>
- <p><a href="vpe/vpe-news-3.3.0.CR1.html">Visual Page
Editor/BrowserSim</a></p>
+ <p><a href="vpe/vpe-news-3.3.0.CR1.html">Visual Page
Editor/BrowserSim</a></p>
</td>
</tr>
<tr>
Added: trunk/documentation/whatsnew/jmx/jmx-news-1.2.0.CR1.html
===================================================================
--- trunk/documentation/whatsnew/jmx/jmx-news-1.2.0.CR1.html (rev
0)
+++ trunk/documentation/whatsnew/jmx/jmx-news-1.2.0.CR1.html 2012-06-06 11:23:49 UTC (rev
41740)
@@ -0,0 +1,82 @@
+<html>
+
+<head>
+<link rel="stylesheet" href="../whatsnew.css">
+<title>JMX Tools 1.2.0.CR1 News</title>
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-17645367-5']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' :
'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+
+</script></head>
+
+<body>
+
+<h1>JMX Tools 1.2.0.CR1 - New and Noteworthy</h1>
+
+ <p align="right"><a href="../index.html">< Main
Index</a> <a href="../jst/jst-news-3.3.0.CR1-full.html">JST/JSF
Tools News ></a></p>
+
+<table border="0" cellpadding="10" cellspacing="0"
width="80%">
+ <tr>
+ <td colspan="2">
+ <hr>
+ <h3>General</h3>
+ <hr>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="left">
+ <p align="right"><b>JMX Support for AS
7.x!</b></td>
+ <td valign="top">
+ <p> Support for JBoss AS 7.x has been completed for this release.
Functioanlly, it will look exactly
+ as it does for AS 6 and below. When you start a server from the JBoss Servers
view, and once
+ the startup completes, the MBean Explorer view will attempt to connect to the
newly started
+ server. Several errors in the core JMX plugins were fixed to allow this.
+ </p>
+ <p> As always, double-clicking on any mbean will allow it to open the editor
for that bean</p>
+ <p><small>
+ Related Jiras: <a
href="https://issues.jboss.org/browse/JBIDE-11483">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11482">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11481">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11064">JBIDE-110...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11872">JBIDE-118...
+ </small></p>
+
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="left">
+ <p align="right"><b>Bugfixes</b></td>
+ <td valign="top">
+<p> Small bugs were fixed as well. Expanding a node in the MBean Explorer will now
use one connection
+ to load the entire tree, rather than using a new connection for each MBean request.
Also, the editor
+ was unable to handle an operation result of type java.lang.Boolean, which caused
errors in the UI for users.
+ A few other small optimizations too place as well. </p>
+ <p><small>
+ Related Jiras: <a
href="https://issues.jboss.org/browse/JBIDE-11484">JBIDE-114...;,
+ <a
href="https://issues.jboss.org/browse/JBIDE-11480">JBIDE-114...
+ </td>
+
+ </tr>
+
+
+</table>
+
+</body>
+
+</html>
+
+
![src="https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921...](http://src="https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png%22){kind=link}
![src="https://issues.jboss.org/secure/attachment/12351312/JBIDE-10464...](http://src="https://issues.jboss.org/secure/attachment/12351312/JBIDE-10464.png%22){kind=link}
![src="https://issues.jboss.org/secure/attachment/12352599/JBIDE-11275...](http://src="https://issues.jboss.org/secure/attachment/12352599/JBIDE-11275.png%22){kind=link}