i haven't done release yet...I've been on vacation just catching up. RC6 will be out this week...JBoss 4.0.4CR2 already has it.
Any chance you can list the version numbers of your lib/ and optional-lib/ dependencies in the embeddable release so we can eliminate version-clash as one source of error? (Maven folks in particular tend to be picky about this.)
Nice news on return from your vacation! Please don't take your winnings and go on another right away, OK? :)
Thanks for all your efforts in this area. EJB3 is super nice.
Versions in the jars are a weak convention that just propagates version info to all docs/build scripts, and has no support from any programatic apis. The version info belongs in the manifest. If you can't use the jdk extcheck -verbose tool to display this info, the jars are broken. All of the ejb3 jars currently are broken:
[starksm@banshee9100 ejb3.deployer]$ for j in *.jar > do > extcheck -verbose $j > done Target file:jboss-annotations-ejb3.jar The target file does not have a specification title Target file:jboss-ejb3.jar The target file does not have a specification title Target file:jboss-ejb3x.jar The target file does not have a specification title [starksm@banshee9100 ejb3.deployer]$
It seems the issue does not mention lib/ dependencies jars. It would be very nice if these jars were fixed as well.