| newbie looking for strategy to deal with *_HOME, ant, junit, "unable to find a java compiler & [message #137598] |
Thu, 29 January 2004 02:29 |
Eclipse User |
|
|
|
Originally posted by: rtayek.no.spam.freightgate.com
hi, converting over from netbeans, trying to integrate some ant scripts into
eclipse (using 3.0.0 or later) so we can build/test/run from within eclipse
(with and without ant) and from ant on the command line. fixed "unable to
find a java compiler" by adding tools.jar, but now getting "bad class file".
usually have some version of 1.4 installed on each machine, but usually need
to target 1.3.1_09. i can probably get these to work by googling some more
as there are threads around that deal with both error messages.
but i am considering using:
<property environment="env"/>
<property file="${user.home}/build.properties"/>
<property file="build.properties"/>
in my ant scripts for maximum flexibily (but i notice that the tomcat 5
sample uses the opposite order).
i hear that eclipse can be started with a jvm and that that or defining
JAVA_HOME will cause the tools.jar to be put into the ant runtime, but i
usualy have no *_HOME's defined and classpath="" but sometimes a jre on the
path and use a batch file or shell script to set *_HOME's and put stuff on
the path.
different developers may have their machines set up differently (but we are
all supposed to use eclipse), so i was looking for a minimally intrusive way
of being able to deal with different versions of jdks, ants, and tomcats,
etc.
we won't be doing this for real for a while, so i am assuing eclipse will
have ant 1.6 by then, but i was wondering what practices those of you who
have been using eclipse for a while have discovered that work well:
any pointers will be appreciated.
thanks
|
|
|
Powered by
FUDForum. Page generated in 0.04123 seconds
] 
Search
Help
Register
Login
Home
