You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/06/22 13:16:00 UTC
[jira] Commented: (MAVEN-442) Reactor does not correctly find resources
The following comment has been added to this issue:
Author: Brett Porter
Created: Sun, 22 Jun 2003 6:14 AM
Body:
I think the best solution is to have the POM store File objects set with getAbsoluteFile, using the basedir on construction. I'll investigate how this will happen, keeping mind Jason's current work on moving to an xmlpull loader for the POM.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-442
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-442
Summary: Reactor does not correctly find resources
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Components:
maven-reactor-plugin
Versions:
1.0-beta-8
1.0-beta-9
Assignee:
Reporter: Bruce Chenoweth
Created: Fri, 23 May 2003 3:00 PM
Updated: Sun, 15 Jun 2003 7:00 PM
Environment: Win2K
Description:
When building sub-projects via the reactor, it appears as though Maven does not process java:jar-resource or test:test-resources correctly.
Example:
Suppose the subproject POM contains:
<resources>
<resource>
<directory>src</directory>
<includes>
<include>**/*.properties</include>
<include>**/*.cfg</include>
</includes>
</resource>
</resources>
When running maven directly from the subproject's base directory, any resource matching the include expressions will be copied from the src directory to the corresponding target location per maven.build.dest.
However, if the same subproject is called via the reactor, these properties will NOT be copied before executing the JUnit testing.
It appears Maven attempts to locate these resources using the base directory of the parent project.
I tried specifying the resource directories using <directory>${basedir}/src</directory>, but that causes problems with other targets when executing maven from the subproject's directory.
---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org