 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
dingfelder
Guest
|
 Posted: Fri Jan 12, 2007 7:51 am Post subject: 2007 output dir (class files vs jar) |
 |
|
I would like to have an output dir that contains just my files that will get deployed, such as the complete jar, a required dll, a property file and a readme.txt file
As it currently stands, when I "run" my project, JBuilder 2007 puts all my class files into a directory structure in the output dir, and I do not want that to get deployed.
Is it safe to say that I need to manually use maven or ant to create a second output dir and I have to manually run this build process to make the jar and put other desired stuff?
And if so, how can I get the maven / ant process to happen automatically when I run the project?
Specifically, I want the "main class" that the run task launches to be executed from within the built jar instead of from the class tree.
Perhaps I am missing something and there is an easier or better way to do this? |
|
| Back to top |
|
 |
Kevin Dean [TeamB]
Guest
|
| Posted: Fri Jan 12, 2007 9:13 am Post subject: Re: 2007 output dir (class files vs jar) |
|
|
dingfelder wrote:
| Quote: | I would like to have an output dir that contains just my files that will
get deployed, such as the complete jar, a required dll, a property file
and a readme.txt file
As it currently stands, when I "run" my project, JBuilder 2007 puts all my
class files into a directory structure in the output dir, and I do not
want that to get deployed.
Is it safe to say that I need to manually use maven or ant to create a
second output dir and I have to manually run this build process to make
the jar and put other desired stuff?
And if so, how can I get the maven / ant process to happen automatically
when I run the project?
Specifically, I want the "main class" that the run task launches to be
executed from within the built jar instead of from the class tree.
Perhaps I am missing something and there is an easier or better way to do
this?
|
The output directory is where compiled classes and copied resources go.
It's an intermediate step to building a JAR file (which I haven't figured
out how to do in JB 2007 yet).
I've never come across a case where running from a JAR file is necessary
in the development environment. If it runs against the output directory,
it should run just fine as a JAR file, assuming you copied all the
required resources.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html |
|
| Back to top |
|
|
Patrick J. Maloney
Guest
|
| Posted: Tue Apr 17, 2007 2:00 am Post subject: Re: 2007 output dir (class files vs jar) |
|
|
"dingfelder" <dingfeldera_nospam (AT) sirtrack (DOT) com> wrote in
news:45a6e986$1 (AT) newsgroups (DOT) borland.com:
| Quote: | Perhaps I am missing something and there is an easier or better way to
do this?
|
Yes, stick with JB2006.
--
Patrick Maloney
New York State Workers' Compensation Board
(Remove REMOVE from e-mail address to reply) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
