This is not unusual. Sometimes the JVM holds a hard ref to some jars, which prevents the
unexplode target from completing fully.
It should not be a problem in most cases, since usually those jars dont change.
In the rare case where it is a prob, just type "seam unexplode" twice on the
commandline. Second try usually works.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015235#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...