Ah, that's easy. Just add a step in your ant build script to copy the generated Jar/Ear/War files to your deploy directory.
If you are compiling on one machine and running JBoss on another, you should probably copy the files to a directory on the deploy machine, and then move them to the deploy directory.
This avoids problems hot-deploying and JBoss only finding half of the file to deploy.
Ciao,
Jonathan O'Connor
Ph: +353 1 872 3305
Mob: +353 86 824 9736
Fax: +353 1 873 3612
| "Michael Mattox" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 12.08.2002 13:42
|
To: <[EMAIL PROTECTED]> cc: Subject: RE : [JBoss-user] Directory structure for using Jboss with Eclipse |
What I'm wanting to do is have eclipse compile the files to a place where JBoss will be looking for them, so they will be deployed automatically. This is how people say they use the hotswapping debugging features but I have no idea how this is actually set up. I'm trying to make the switch from JBuilder to Eclipse.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jonathan.O'[EMAIL PROTECTED]
Sent: Monday, August 12, 2002 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Directory structure for using Jboss with Eclipse
Michael,
I'm not sure if I can help, but here's what we do with JBoss and Eclipse.
We have our own ANT build script which can run outside of all IDEs. We set up an external run command to run this script for a full build.
It has its own dirctory structure with build directories for any generated files including XDOCLET generated code.
We point the eclipse project settings to our source directory and the src-gen directory created by our build script.
When we do a full build, Eclipse will recompile all sources into its own build directory, and all those errors and warnings are generated at the point.
I don't bother with EASIE JBoss plug in, but I don't think that's relevant to your question.
Ciao,
Jonathan O'Connor
Ph: +353 1 872 3305
Mob: +353 86 824 9736
Fax: +353 1 873 3612
