Paths vs. properties in Ant scripts [closed]?

Up vote 0 down vote favorite share g+ share fb share tw.

As I see it, the main properties of paths (as opposed to properties) in Ant are: Better for scripts which run on different OS's (platform-independent). Can't be overridden from the command line. Require slightly long-winded "${toString:pathname}" syntax whenever a path string is required.

Easier to read when concatenating together multiple paths (e.g. For classpaths). Point 1 isn't a consideration for my team, nor is it ever likely to be. I'm also not too worried about people overriding properties from the command line.

With that in mind I'm leaning towards using properties for everything except the classpaths. Am I missing something? What rule(s) of thumb do you use when deciding to use paths instead of properties?

Ant link|improve this question asked Mar 8 at 15:06Baqueta90827 71% accept rate.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.