ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18700] - Stange classpath problem
Date Mon, 07 Apr 2003 06:46:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18700>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Stange classpath problem

nicolas.mailhot@laposte.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From nicolas.mailhot@laposte.net  2003-04-07 06:46 -------
Well, I had more or less figured it for myself.
Moving the property part in a refided classpath that is defined in a target
executed after the loadproperties works.

However there is a big consistency problem.

The rest of the classpath references files that do not exist yet (since they
will be generated later), but ant has no problem defering resolution till the
classpath is actually used. Not doing the same for properties is confusing, and
you end up with bits of classpath scattered all over the build file wich makes
debuging a lot harder than it should be.

These classpathes are top-level, not defined into a target. Resolving them out
of targets where they can not be used anyway seems like an implementation problem.

Anyway it works now and I'll try not to forget this ant quirk, so you can close
this if you disagree.

Mime
View raw message