The grails plugin sometimes returns 404 for first request

[GoogleCodeExporter]

There is definitely a problem - it just doesn't always happen. It seems that 
sometimes, the first request fails with a 404. You can see that in Travis CI 
https://travis-ci.org/wro4j/wro4j-grails-plugin/builds/17555086 I noticed this 
as I'm trying to release version 1.7.3 of the wro4j-grails-plugin, but I can't 
get the build to successfully complete consistently. Earlier today, I got one 
build to succeed... but after that, despite not making any changes, I haven't 
gotten a success. There must be a race condition in here somewhere... I hope 
this gives you a hint, and at least there's an easily reproducible test.

Original issue reported on code.google.com by alex.obj...@gmail.com on 26 Jan 2014 at 9:31

[GoogleCodeExporter]

Original comment by alex.obj...@gmail.com on 29 Jan 2014 at 4:28

• Changed title: The grails plugin sometimes returns 404 for first request

[GoogleCodeExporter]

I'm confident this isn't a problem that's isolated to the Grails plugin. If you 
want, I can reproduce it using a different setup if you provide me with a 
sample project (I think all you need is the basic WRO setup + WroContextFilter).

Original comment by candrews...@gmail.com on 29 Jan 2014 at 5:45

[GoogleCodeExporter]

I was able to reproduce it in isolation as well. I have a fix already, but
need to write few more tests. I will publish a snapshot very soon and will
let you know.

Original comment by alex.obj...@gmail.com on 29 Jan 2014 at 5:54

[GoogleCodeExporter]

Fixed in branch 1.7.x.

Original comment by alex.obj...@gmail.com on 30 Jan 2014 at 9:48

• Changed state: Fixed

[GoogleCodeExporter]

@candrewsintegralblue A snapshot should be available shortly on sonatype 
repository. Let me know if you find any issues with it.

Original comment by alex.obj...@gmail.com on 30 Jan 2014 at 9:52

[GoogleCodeExporter]

I just bumped wro4j-grails-plugin 1.7.4-SNAPSHOT to use wro4j 1.7.4-SNAPSHOT. I 
ran the build twice, and both times it succeeded. So the evidence seems to 
indicate that the problem has been solved :)

Original comment by candrews...@gmail.com on 30 Jan 2014 at 3:39

[GoogleCodeExporter]

Indeed, but while testing it with wro4j-grails-plugin, I have noticed the 
following bug: issue838
Wondering if you can reproduce it yourself when resourceWatcherAsync=true

Original comment by alex.obj...@gmail.com on 30 Jan 2014 at 3:42