On 25/04/2011 08:39, Unico Hommes wrote:
The only way I see ATM for a faster development cycle is to use
something like JRebel.
Hmmm... I don't like the sound of that. JRebel is $189, that's rather
alot for someone just wanting to do a few quick fixes. I'd rather we
were configured in such a way as to be able to use whatever tools are
common and thus attract as many developers as possible.
Is this possible with Maven? Still exploring.
Ross
--
Unico
On Sun, Apr 24, 2011 at 2:59 AM, Ross Gardler<[email protected]> wrote:
On 24/04/2011 01:31, Ross Gardler wrote:
On 24/04/2011 00:35, Ross Gardler wrote:
On 23/04/2011 23:07, Ross Gardler wrote:
...
I'll keep digging when I find a little more time, but if anyone sees my
silly mistake please let me know.
Getting a little closer, but still not working...
I tried running from the projects context sensitive menu rather than the
server controller view. This opened the browser for me at
http://localhost:8080/rave-portal and the page loaded (with 404's for each
gadget as the URL for them is not relative.
I'm going to bed now, I hope someone can provide me with a simple step by
step process for getting this working in Eclipse for an efficient edit/build
cycle.
(Damn those steep learning curves with new build tools.)
Ross
[1]
http://joemorrison.org/blog/2008/06/01/developing-web-applications-with-maven-and-eclipse-you-can-have-it-all/
