The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Tue, 23 Mar 2004 7:13 PM
Changes:
environment changed to
Fix Version changed to 1.1
Fix Version changed from 1.0-rc3
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1016&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1016
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1016
Summary: Test case of extending a project on several levels
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
inheritance
Fix Fors:
1.1
Versions:
1.0-rc1
Assignee:
Reporter: Dominik Roblek
Created: Mon, 10 Nov 2003 1:15 AM
Updated: Tue, 23 Mar 2004 7:13 PM
Description:
I've created a very minimalistic project inheritance test case, which should work.
Unpack the attached project.zip, go to project-a/project-b/project-c subdirectory and
try to execute "maven java:compile". It should succeed when the possibility of
extending a project on several levels would be implemented but currently it fails
since it does not see dependency specified in project-a's POM.
---------------------------------------------------------------------
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/secure/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]
