> From: Jacob Kjome [mailto:[EMAIL PROTECTED] > > Now, to the original point of <path>'s defined in <xmlproperty> not > working like > <path's> defined elsewhere. I define my dependencies in an <xmlproperty> > file > and make use of the ability to define <path>'s in that same <xmlproperty> > file. > It keeps things together and keeps my main build file clean of this > configuration information. I hardly ever have to touch my generic build > file > that I import into other projects. I just have the generic build file > load the > <xmlproperty> file and update the <xmlproperty> file as needed. It has > worked > very well until I ran into this issue. > > The bottom line is, shouldn't a <path> defined in <xmlproperty> work > identically > to a <path> defined directly in a build file? Any response that doesn't > directly answer this question is missing the point. And please see my > original > email for an example of the issue. I'm hoping this can be fixed before > the > next release of Ant.
Sorry for missing the point again ;-) XML or .properties syntax for properties *is* irrelevant. But defining Ant paths in XML properties files is not. This was a hack IMHO, and it may indeed by possible to fix it to behave just as if it was defined in the build file... Did you read that? Just as in the build file! So just do it in an *actual* build that you import, instead of xmlproperty. You are thus guaranteed it will behave *as in* a build file ;-) Also, glad to hear import allows you do have a nice generic build file. But what prevents you for putting the Path info in the lightweight importing build file then? It's the project specific build file at this point, no? OK, OK, I won't barge in to your thread anymore. I personally avoid too many levels of indirection, but that's just me. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
