Jan Beernink wrote:
I've also noticed the issue of seemingly random libraries being listed as deployable modules in the servers view. After I did some investigating, I noticed that all of the libraries listed as deployable module contained a Main-Class entry in their manifest file.
Great find! This seems indeed to be the case. Almost all of the libraries I mentioned earlier indeed have this main class listed!
More precisely, the ones I mentioned that have "J2EE Application Client Module" when I hover with the mouse over them are the ones who have this Main-Class entry.
The one that said "J2EE EJB Module" doesn't have this Main-Class, but it does have classes with EJB annotations. However, since this particular jar is in the EAR/lib directory, it doesn't seem JBoss tools has to do anything special with it regarding deployment.
After I upgraded to JBoss tools 3.2 CR1 I now get the following in my log after I do a clean/full deploy:
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:39.610
!MESSAGE Module my_main published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:39.614
!MESSAGE Module jbosscache-core.jar published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:39.618
!MESSAGE Module jgroups.jar published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:39.627
!MESSAGE Module my_ejb_client.jar published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:39.670
!MESSAGE Module some_main_ejb published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:40.238
!MESSAGE Module my_main_web published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:40.249
!MESSAGE Module jxl.jar published without error.
!ENTRY org.jboss.ide.eclipse.as.core 0 33685505 2011-02-16 13:15:40.265
!MESSAGE Module saxon9.jar published without error.
In this case, the actual deployment that is copied to JBoss AS is simply:
my_main
my_main_ejb
my_main_web
lib
jbosscache-core.jar
jgroups.jar
some_ejb_client.jar
commons-codec.jar
... [bunch of other jars]
joda-time.jar
As can be seen, the jars that are somehow treated "differently' by the deployer all simply end up in my_main/lib. It's highly confusing that the deployer as well as the GUI treats them differently.
Since CR1 is does say "published without error" now. Unfortunately, it still hapens that when I save a single file, the deployer suddenly pulishes 1000+ other files, and eventually this gives me a deployment with lots of deleted (missing) files as I have been seeing since the first beta versions of JBoss tools 3.2.
I've also now confirmed seeing the problem on a completely different machine, but same project (different OS too: Unbuntu vs OS X), so this would rule out a local installation problem.