[ANN] JBoss Integration Plugin 1.10 released

Bug fixes:
- Error with settings dialog in classic view corrected.

Versions 1.8 and 1.9 had a nasty bug which prevented the settings dialog from being dismissed when using classic view. You should immediately update to version 1.10 if you have already installed one of these versions.

After starting IDEA please go straight to the plugin configuration panel, update the JBoss Integration plugin to version 1.10, and confirm to restart IDEA immediately when asked to. Don't do anything else between, unless you have to kill IDEA externally to get rid of the settings dialog. Sorry for any inconvenience.

3 comments
Comment actions Permalink

On a somewhat related note - is it/should it/will it
be possible to run
from the exploded directories? Or doesn't
deploy-through-JMX support
this? Reason I ask is that this project I'm working
on is a fairly
complex one, and creating the different jars/wars,
and resulting ear
takes a fair amount of time. Just wondered if
redeploying from exploded
dirs would be faster.


Unfortunately IDEA doesn't allow to set the exploded directory as deployment source for remote run configurations - http://www.intellij.net/tracker/idea/viewSCR?publicId=42014 .
But for local run configurations you can use the exploded directory. You just have to name the exploded directory correctly (*.jar, *.war, *.ear) in order for JBoss to recognize its type.

Also, does the plugin, or IDEA itself create the
deployment packages?
Every new deployment leaves a slew of *.tmp files
behind (that never get
cleaned up).


What do you mean by deployment packages? And where are those *.tmp files located?

0
Comment actions Permalink

Martin Fuhrer wrote:

local run configurations you can use the exploded directory. You just
have to name the exploded directory correctly (*.jar, *.war, *.ear)
in order for JBoss to recognize its type.


Wow. That simple, huh? :) Works like a charm. Thanks!

>> Also, does the plugin, or IDEA itself create the deployment
>> packages? Every new deployment leaves a slew of *.tmp files behind
>> (that never get cleaned up).

What do you mean by deployment packages? And where are those *.tmp
files located?


I mean the *.ear, *.war, *,jars created during a build . The project I'm
working on consists of 6 java modules, 3 web modules, 1 ejb module, all
packaged into one ear. When I do a build, a series of .jar files named
"___]]>.tmp" are generated in my /tmp dir (I work under
linux) - one for every java module, and one for the .ear module.
Every new build generates a new set, and they are never cleaned up.
I assume it's the build process in IDEA that generates these, but wanted
to make sure before I file a bug.

CU,
Edwin

0
Comment actions Permalink

That's definitively an IDEA issue without any control from the plugin. So please feel free to file a bug.

0

Please sign in to leave a comment.