JBoss4 installation weirdness

[Panagiotis Astithas]

As I found out the hard way today, jboss4 installs different things 
depending on whether it is being built using jdk14 or jdk15. In the 
latter case you get EJB3 stuff that (unfortunately for me) include old 
versions of commons-stuff which may create conflicts with a deployed 
app, thanks to the funky jboss classloader architecture. The binaries 
that jboss.com ships evidently contain stuff that you get when you build 
with jdk14.

I'm not sure if it is possible or even reasonable to change the current 
behavior (I'm overriding JAVA_PREFERRED_PORTS), but perhaps we could add 
an informative message when building the port to inform the user.


Cheers,
Panagiotis