Hi all,
I wanted to gather some thoughts on ${basedir} usage in
project.xml/maven.xml and how it relates to the reactor. This will help
clear up the problems in MAVEN-442.
The following tags in project.xml potentially can be used as relative
paths:
<extend>
<*sourceDirectory> (ie includeing unit tests, etc)
<directory> (under resource)
(and <filters> - see my next proposal :)
There are two alternatives:
1) assume all of these paths are relative to project.xml.
2) require all to be absolute paths (using basedir where needed to know
where project.xml lives).
In either case, ${basedir} will always be an absolute path that
specifies the directory containing project.xml/maven.xml.
Any plugins (and custom jelly maven.xml scripts) that don't work with
the choice will need to be modified.
Can anyone see any problems with either case, or provide favourable
reasons for either? This bug is currently blocking RC1, so I'd like to
decide and implement soon - either one should be fairly brief.
Cheers,
Brett
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
