ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 2611] - Automatic modification of standard classpath
Date Tue, 31 Jul 2001 06:11:46 GMT
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2611

*** shadow/2611	Mon Jul 30 07:25:40 2001
--- shadow/2611.tmp.6806	Mon Jul 30 23:11:46 2001
***************
*** 2,9 ****
  | Automatic modification of standard classpath                               |
  +----------------------------------------------------------------------------+
  |        Bug #: 2611                        Product: Ant                     |
! |       Status: RESOLVED                    Version: 1.3                     |
! |   Resolution: WONTFIX                    Platform: Other                   |
  |     Severity: Enhancement              OS/Version: Other                   |
  |     Priority: Other                     Component: Core                    |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | Automatic modification of standard classpath                               |
  +----------------------------------------------------------------------------+
  |        Bug #: 2611                        Product: Ant                     |
! |       Status: REOPENED                    Version: 1.3                     |
! |   Resolution:                            Platform: Other                   |
  |     Severity: Enhancement              OS/Version: Other                   |
  |     Priority: Other                     Component: Core                    |
  +----------------------------------------------------------------------------+
***************
*** 38,41 ****
  property for a description of this behaviour (This is in the 1.4 docs).
  
  I have never seen the need to include ${java.class.path}. In fact, I run with 
! an empty classpath.
--- 38,59 ----
  property for a description of this behaviour (This is in the 1.4 docs).
  
  I have never seen the need to include ${java.class.path}. In fact, I run with 
! an empty classpath.
! 
! ------- Additional Comments From boris@i3.informatik.rwth-aachen.de  2001-07-30 23:11 -------
! It seems that you are setting up your CLASSPATH externally (e.g. in the shell
! which invokes Ant.
! 
! In my case it is different. All libraries which are required to compile the 
! project are stored in the directory `lib'. The libraries in this directory won't 
! be added to the CLASSPATH in the shell that invokes Ant. I'm using java.class.path 
! in the pathelement just for convenience if any one likes to setup his own 
! CLASSPATH, e.g. for testing if a newer version of a library in the lib directory
! can be  used with the project.
! 
! Unfortunately the classpath I defined is not used by default since Ant's tasks
! can only use the classpath which has been defined by the time Ant has been
! invoked. As you can see from the above description there is no way to set the
! classpath in the shell. I know that a shell script can do this, but I don't like
! this because everything that can be done easily in the build.xml file should be 
! there. In my opinion this avoids mixing of responsibilities.

Mime
View raw message