You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2001/07/30 16:25:40 UTC
[Bug 2611] - Automatic modification of standard classpath
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 Fri Jul 13 02:34:50 2001
--- shadow/2611.tmp.24123 Mon Jul 30 07:25:40 2001
***************
*** 2,9 ****
| Automatic modification of standard classpath |
+----------------------------------------------------------------------------+
| Bug #: 2611 Product: Ant |
! | Status: NEW Version: 1.3 |
! | Resolution: Platform: Other |
| Severity: Enhancement OS/Version: Other |
| Priority: Other Component: Core |
+----------------------------------------------------------------------------+
--- 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 |
+----------------------------------------------------------------------------+
***************
*** 30,33 ****
Would it possible to define a task which automatically modifies the classpath
for all other tasks or to modify the standard classpath automatically if a path
! with a certain id is modified?
--- 30,41 ----
Would it possible to define a task which automatically modifies the classpath
for all other tasks or to modify the standard classpath automatically if a path
! with a certain id is modified?
!
! ------- Additional Comments From conor@cortexebusiness.com.au 2001-07-30 07:25 -------
! Ant automatcially includes the standard classpath in the path used in certain
! circumstances (<java> task, etc). Please refer to the build.sysclasspath
! 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.