The following comment has been added to this issue:
Author: Brett Porter
Created: Sun, 29 Jun 2003 9:44 PM
Body:
> I thought it was the opposite. We currently are expecting
> sourceDirectory to be absolute.
sourceDirectory will be absolute once loaded (File object will be made absolute by
prepending ${basedir} - we can never use relative File objects). However I believe the
specification in the POM does not need the basedir and is potential mail list flooder
:)
I'm happy to change this to requiring ${basedir} and giving a deprecation mesage (but
working) on relative paths, but it seems unnecessary. More people will play with
project.xml than maven.xml.
>>- all properties that specify files and use of files in maven.xml will
>> have to have ${basedir} or absolute paths as there is no way to track
>> CWD from there, or to know which properties are files.
> Why is this different from project.xml? I'm not sure I understand why > paths in
> maven.xml can't be relative to it's project.xml.
This is just my understanding, but wouldn't Jelly need to be made aware of ${basedir}
and handle that?
> Is project.xml still optional to run Maven? It currently is.
Yes, this doesn't change that.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-522
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-522
Summary: Clarification of POM elements that use paths.
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Assignee:
Reporter: Jason van Zyl
Created: Sat, 28 Jun 2003 8:13 AM
Updated: Sat, 28 Jun 2003 8:13 AM
Description:
Currently there are several elements in the POM that use paths in order to find
various resources. The currently accepted pattern is to use ${basedir} as a prefix for
all these paths so that they work in the reactor environment. We can certainly
identify all the elements in the POM that are path related. We need to decide whether
to mandate the use of ${basedir} or make it implicit in POM elements that store paths.
Once this is decided the plugins all need to be audited to ensure they follow the
pattern we mandate.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
