Hi there,
The same thing is happening to me, and the combined with the Ant Groovyc
task not checking if the file has been modified or not and always
recompiling, it's quite a pain.
However, if I'm not mistaken, I think hotswapping is enabled by Resin
but provided by Java itself, so we might
I do, but I compile all my groovy code into classes with Ant and embed them in
our .war file deployment (We're mostly Java). I haven't tried to run groovy
scripts directly like you mention - I believe I did get a demo of grails going
at one point, but it was probably 3.1.3.
Ryan
- Original
Yeah, it works for me too all pre-compiled, but I'm trying to get a better
development environment.
Resin will compile your java classes and reload changes and supposedly do
this with groovy too, but I've not been able to get it to work.
bumzee wrote:
Is anyone successfully using Groovy with
I've installed Resin 3.2.0 in a minimal CentOS running inside VMWare Player
2.5, but I can't hit the running Resin in the VM from the host machine.
The VM is running in 'Bridged' mode, so it grabs a DHCP-assigned IP address
for the local LAN. I can SSH into the VM through that IP address. I can
you checked all the obvious stuff like iptables config, etc.? I use
vmware ws for resin dev, running FC6. works good.
Michael Prescott wrote:
I've installed Resin 3.2.0 in a minimal CentOS running inside VMWare
Player 2.5, but I can't hit the running Resin in the VM from the host
machine.
Is anyone successfully using Groovy with Resin ?
What does your resin.conf look like ?
This is on the resin website, but it doesn't work for me in 3.1.5.
When it gets to a groovy file the compilation just stops or times out.
resin.conf
web-app-default
class-loader
No, of course not! I come from the world of Windows, where servers are an
implied donation to the botnet community. Closed source, open ports. :-)
Thanks for the tip, that was the problem.
Michael
On Tue, Oct 14, 2008 at 4:56 PM, Martin Crundall [EMAIL PROTECTED]wrote:
you checked all the
Since it's not marked on the bug in Mantis, and I can't remember, was
this issue found in the 3.0.x tree? If so, does it affect all versions?
Thanks,
Matt
[EMAIL PROTECTED] wrote:
The following issue has been CLOSED
==
