Mark H. Wilkinson wrote:
On Mon, 2003-06-23 at 14:42, Brett Porter wrote:
There are two alternatives: 1) assume all of these paths are relative to project.xml.
I'd vote for this one unless someone can explain...
If you vote for this one, do you also allow ${basedir}?
2) require all to be absolute paths (using basedir where needed to know where project.xml lives).
... under what circumstances project.xml should contain an absolute path that doesn't start with ${basedir}.
I can't think of any to be honest. I was thinking of letting Maven silently convert relative paths to absolute ones by adding basedir to the front, but I'm worried about the inconsistency of allowing basedir and not.
Also, when we get to jelly scripts like maven.xml, it gets harder (if possible?) to preprocess relative paths, so ${basedir} is then required. However, this is likely to generate less complaints on the user list as fewer people do any jelly scripting for their builds :)
I wonder though - if all the examples have ${basedir} and the FAQ has "why don't my relative paths work?", whether there would be too many problems? Maybe I'm too much of an optimist :)
Cheers, Brett
-- Web Developer f2 network ~ everything essential 02 8596 4437
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
