Jonathan Gallimore kirjoitti:
In theory uninstalling and installing again is all you need. Are you
running Ganymede? I've had lots of problems with stuff from the update
site being cached in Ganymede, and as yet, I haven't found a solution.
Anyone got any ideas?
Updating the version number might help Ganymede figure out that the
contents have been updated :P
Jon
Alex Grönholm wrote:
Jonathan Gallimore kirjoitti:
I've committed this change and updated the update site.
What do I need to do to get a new version? I just uninstalled &
reinstalled from the update site, but it still only includes those
same three jars.
Jon
Jonathan Gallimore wrote:
Hi Alex,
Thanks for downloading the plugin and giving it a go. I guess at
the moment, we'd regard it as beta. I'm currently working on a
couple of final features and was then going to see if everybody
thought it was ready for a release.
In terms of the classpath, you're right, we only add
openejb-client, javaee-api and optionally ejb31-api-experimental if
you want it. It hasn't caused me any problems with testing
(probably because I deploy to a standalone server and hit the beans
as if I'm a remote client when I'm testing the plugin). I'm
certainly happy to add the other jars in the openejb/lib folder to
the project classpath. If there's no objections, I'll probably be
able to get the change committed and the update site updated this
evening.
Jon
Alex Grönholm wrote:
I recently installed the "Apache OpenEJB WTP Runtime 1.0.0" and
found that it only includes a few libraries when added to a
project. In my opinion, the runtime should add all of the
libraries from openejb/lib to the project, like the JBoss runtime
does. This is necessary for, among other things, unit testing
since all of the server's requisites must be on the classpath. I
do not know the current state of affairs with the plugin, so could
someone comment on this please?
