The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Sun, 24 Oct 2004 2:27 PM
Comment:
Here is a condensed patch with all the changes, plus a test case and additional check
if the directory exists.
I haven't commit it though, for a reason: once this new properties gets through, users
will expect a mechanismo to include/exclude files, probably using wildcards (like *
and **). So, I change the property to cactus.resources.dirs, in a way that would allow
us to add new properties in the future (like cactus.resources.includes and
cactus.resources.excludes). Note that this is not as straightfoward as having this
info in the POM, as we cannot have individual includes/excludes for each directory.
Anyway, I will commit (or not) the changes once I get some feedback on this comment.
-- Felipe
PS: another improvement that could be made would be not relying on maven.build.dest
and including the resources directly from inside the <cactifywar> tag. But I'm not
sure if that would work (besides I haven't the spare cycles to check it right now :-)
Changes:
Attachment changed to CACTUS-132-felipeal.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-132?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-132
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-132
Summary: Allow cactus plugin to include some resources
Type: New Feature
Status: Open
Priority: Minor
Project: Cactus
Components:
Maven Integration
Assignee: Felipe Leme
Reporter: Nicolas Chalumeau
Created: Tue, 20 Jul 2004 5:18 AM
Updated: Sun, 24 Oct 2004 2:27 PM
Description:
In a project I produce a jar artifact. I have a webapp in my src/test/webapp
directory. I need to include some resources in the war for the cactus test as junit
does.
As Vincent answers me :
> Is there a way to include build resources and test resources in the
> webapp during a cactus test ?
... I guess the Cactus
plugin could copy some resources. However, the resources that Cactus would
copy (during the cactifywar step) would need to be defined as properties
(and not in the POM as there's not way currently to extend the POM and I
think we shouldn't reuse the junit resources which are for pure JUnit
tests).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/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]
