[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas Chalumeau (JIRA)]

 [ http://issues.apache.org/jira/browse/CACTUS-132?page=history ]

Nicolas Chalumeau updated CACTUS-132:
-

Attachment: test06.zip

I can't include this in the global patch so this is the zip of the test case.

I find something strange :
- when i am in the test06 dir and i launch cactus:test, the test are okay
- but when i am in maven dir and launch plugin:test, the test fail

In fact i see this before. The reactor seem to use for relative path it use as base 
path maven. ie :
When the copy of resource it looks for 
.../integration/maven/target/classes/test.properties and not for 
.../integration/maven/src/plugin-test/test06/target/classes/test.properties for the 
target dir

That's why plugin:test fail. Can't the pluginTest use the maven:maven tag could solve 
it ?

Nicolas,

> Allow cactus plugin to include some resources
> -
>
>  Key: CACTUS-132
>  URL: http://issues.apache.org/jira/browse/CACTUS-132
>  Project: Cactus
> Type: New Feature
>   Components: Maven Integration
> Reporter: Nicolas Chalumeau
> Assignee: Felipe Leme
> Priority: Minor
>  Attachments: CACTUS-132-felipeal.patch, CACTUS-132-felipeal.patch2, 
> CACTUS-132-nchalumeau.patch, changes.xml.diff, plugin.jelly.diff, 
> plugin.properties.diff, project.xml.diff, properties.xml.diff, test06.zip, webjar.zip
>
> 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).

-- 
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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas Chalumeau (JIRA)]

 [ http://issues.apache.org/jira/browse/CACTUS-132?page=history ]

Nicolas Chalumeau updated CACTUS-132:
-

Attachment: CACTUS-132-nchalumeau.patch

Add the global patch.
The following properties are add :
# (optional). List of resources label to include in the war classpath
cactus.resources.dirs=

# (optional). Label directory to include in the war classpath
#cactus.resources.X.dir=src/main/resources

# (optional). Regular expression for the label X that file have to match to be include 
in the war classpath. by default **/*
#cactus.resources.X.includes=**.xml,**.dtd

# (optional). Regular expression for the label X that file have to match to be exclude 
in the war classpath. by default none
#cactus.resources.X.excludes=

The includes/excludes regexp work and allow "recursive" includes by default.

test follow

> Allow cactus plugin to include some resources
> -
>
>  Key: CACTUS-132
>  URL: http://issues.apache.org/jira/browse/CACTUS-132
>  Project: Cactus
> Type: New Feature
>   Components: Maven Integration
> Reporter: Nicolas Chalumeau
> Assignee: Felipe Leme
> Priority: Minor
>  Attachments: CACTUS-132-felipeal.patch, CACTUS-132-felipeal.patch2, 
> CACTUS-132-nchalumeau.patch, changes.xml.diff, plugin.jelly.diff, 
> plugin.properties.diff, project.xml.diff, properties.xml.diff, webjar.zip
>
> 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).

-- 
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]

Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Felipe Leme]

On Wed, 2004-10-27 at 06:10, [EMAIL PROTECTED] wrote:
> I think the default is "nothing" : an empty cactus.resources.dirs list by 
> default to don't break project who don't use this feathure. 

Actually, I was more worried about possible include/exclude conflicts,
but I guess I was overestimating the problem.

> Do you want me to attach the patch to this issue or create a new one ?

Use this same issue.

> Do you want the patch include the CACTUS-132 modification ?

My latest patch would be a 'jumpstart' for your new modification, as it
already adds a new test case structutre, documentation, etc... But after
you're done, you just create a new patch.

-- Felipe


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas . CHALUMEAU]

>> Why not using this king of thing ?
>> cactus.resources.dirs=logResources,otherResources
>> cactus.resources.logResources=src/main/resources/log
>> cactus.resources.logResources.includes=**.xml,**.dtd
>> cactus.resources.logResources.excludes=**old.*
>
> Hmm, I don't like this kind of 'XML linearization', 

I agree with you, this kind of thing are easy ununderstandable.

> but I think we don't
> have other option (as this is a POM limitation). We just need to make
> sure we can define the corner cases (like, what's the default,
> everything?).

I think the default is "nothing" : an empty cactus.resources.dirs list by 
default to don't break project who don't use this feathure. 

>
>> If you want i can take a look at this and send you the result ...
>
> For me it's fine - if you provide a new patch with these changes and the
> proper test cases and documentation (on properties.xml), I will be glad
> to apply it.

Do you want me to attach the patch to this issue or create a new one ?
Do you want the patch include the CACTUS-132 modification ?

Nicolas,

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Felipe Leme (JIRA)]

 [ http://issues.apache.org/jira/browse/CACTUS-132?page=history ]

Felipe Leme updated CACTUS-132:
---

Attachment: CACTUS-132-felipeal.patch2

Polished some documentation and updated with CVS (because of CACTUS-132 fix).

> Allow cactus plugin to include some resources
> -
>
>  Key: CACTUS-132
>  URL: http://issues.apache.org/jira/browse/CACTUS-132
>  Project: Cactus
> Type: New Feature
>   Components: Maven Integration
> Reporter: Nicolas Chalumeau
> Assignee: Felipe Leme
> Priority: Minor
>  Attachments: CACTUS-132-felipeal.patch, CACTUS-132-felipeal.patch2, 
> changes.xml.diff, plugin.jelly.diff, plugin.properties.diff, project.xml.diff, 
> properties.xml.diff, webjar.zip
>
> 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).

-- 
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]

Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Felipe Leme]

On Tue, 2004-10-26 at 06:08, [EMAIL PROTECTED] wrote:
> I think it could be easy to do by adding includes and exclude in the 
> ant:copy task.

It might be, I just haven't tried yet.

> Why not using this king of thing ?
> cactus.resources.dirs=logResources,otherResources
> cactus.resources.logResources=src/main/resources/log
> cactus.resources.logResources.includes=**.xml,**.dtd
> cactus.resources.logResources.excludes=**old.*

Hmm, I don't like this kind of 'XML linearization', but I think we don't
have other option (as this is a POM limitation). We just need to make
sure we can define the corner cases (like, what's the default,
everything?).

> If you want i can take a look at this and send you the result ...

For me it's fine - if you provide a new patch with these changes and the
proper test cases and documentation (on properties.xml), I will be glad
to apply it.

> Of course I am for applying this patch as I really need this 
> fonctionnality and actully we use a modify plugin.jelly so I need to do 
> the modification for new release (no one actually :) )

I'm using that modified patch at work too, so I'm eager to fix this bug.
But we must be careful when we include such new features.

> > PS: another improvement that could be made would be not relying on
> > maven.build.dest and including the resources directly from inside 
> > the  tag.
> Good approach. But is this fonctionnality could be use with  
> too ?

Guess so.

-- Felipe



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas . CHALUMEAU]

> Here is a condensed patch with all the changes, plus a 
> test case and additional check if the directory exists.

Cool :)

> 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 **). 

I think it could be easy to do by adding includes and exclude in the 
ant:copy task.

> 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.

Why not using this king of thing ?
cactus.resources.dirs=logResources,otherResources

cactus.resources.logResources=src/main/resources/log
cactus.resources.logResources.includes=**.xml,**.dtd
cactus.resources.logResources.excludes=**old.*

cactus.resources.otherResources=src/main/resources/other
cactus.resources.otherResources.includes=**.xml,**.dtd
cactus.resources.otherResources.excludes=**old.*

If you want i can take a look at this and send you the result ...

> Anyway, I will commit (or not) the changes once I get some feedback 
> on this comment.

Of course I am for applying this patch as I really need this 
fonctionnality and actully we use a modify plugin.jelly so I need to do 
the modification for new release (no one actually :) )

> -- Felipe
>
> PS: another improvement that could be made would be not relying on
> maven.build.dest and including the resources directly from inside 
> the  tag.

Good approach. But is this fonctionnality could be use with  
too ?

> But I'm not sure if that would work (besides
> I haven't the spare cycles to check it right now :-)

Nicolas,

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

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  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]

RE: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas . CHALUMEAU]

Hi Vincent,

> Hi Nicolas,
>
> Thanks for those patches. I haven't had a look yet (I'm still on holiday
> till the 8th of August and I'm trying to do things other than coding...
> ;-)).
Me too ;-) the 8th of August

> As soon as I'm back I'll check them out (I may possibly do it earlier
> if I get bored before the end of the holidays).
Bored during holidays !!

> As for Strutstescase, I'm unsure. The point is that the strutstestcase
> project is a separate project. It has nothing to do with the Cactus 
project
> (apart from the fact that it extends Cactus). I have no knowledge of it
> either. Thus I am loathe to include a dependency to it as there'll be 
stuff
> to fix or modify and I won't be able to do it. Thus the sample will 
become
> unsupported and will be broken (that's also the problem of OSS projects
> accepting all contributions without maintainers for them).
I will write an other sample or include a test in the existing one in that 
case. In fact I just need to do a copy paste in an existing test.

> In view of all this I think it makes more sense that you sample belongs 
to
> the strutstestcase project itself rather than to the Cactus project.
>
> What do you think?
This sample is trivial and the strutstestcase include some more signifiant 
example. Integrate strutstestcase with Cactus is as simple as doing some 
Jsp/Servlet Test, it is just the way to write test and you don't have any 
thing to configure, just launch Cactus ...

> Thanks
> -Vincent

Nicolas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Vincent Massol]

Hi Nicolas,

Thanks for those patches. I haven't had a look yet (I'm still on holiday
till the 8th of August and I'm trying to do things other than coding...
;-)). As soon as I'm back I'll check them out (I may possibly do it earlier
if I get bored before the end of the holidays).

As for Strutstescase, I'm unsure. The point is that the strutstestcase
project is a separate project. It has nothing to do with the Cactus project
(apart from the fact that it extends Cactus). I have no knowledge of it
either. Thus I am loathe to include a dependency to it as there'll be stuff
to fix or modify and I won't be able to do it. Thus the sample will become
unsupported and will be broken (that's also the problem of OSS projects
accepting all contributions without maintainers for them).

In view of all this I think it makes more sense that you sample belongs to
the strutstestcase project itself rather than to the Cactus project.

What do you think?

Thanks
-Vincent

> -Original Message-
> From: Nicolas Chalumeau [mailto:[EMAIL PROTECTED]
> Sent: jeudi 29 juillet 2004 21:47
> To: [EMAIL PROTECTED]
> Subject: Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include
> some resources
> 
> Hi Vincent
> 
> Look after for my comment :
> 
> > Hi Nicolas,
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED] [mailto:[EMAIL <mailto:%5BEMAIL> PROTECTED]
> >> trelaze.com]
> >> Sent: mercredi 28 juillet 2004 10:37
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: [jira] Commented: (CACTUS-132) Allow cactus plugin to
> >> include
> >> some resources
> >>
> >> Ok pas de probleme. Do you want I modify one of the samples
> >> application to
> >> illustrate that UC or is there a better way to do some test case in the
> >> maven plugin.
> >
> >
> > It's hard to write unit tests for maven plugins. I'm not sure what we
> > can do
> > to test your new feature (resource copying).
> 
> I am curious on how to do this so I could try to do it if you want. I
> think that using the plugin:test goal should work to call cactus task in
> the sample applications with the reactor or multiproject. The call could
> be iterate on each type of server... Of course I don't have all the
> servers that cactus support but I could enable a plugin test for tomcat
> and jboss and make it extensible by using a property list of server.
> 
> > We could of course modify one
> > of the existing sample so that it does some resource copying but I can't
> > think of a valid use case that would also be meaningful as an example.
> 
> I add a new sample. It is meaningful as it is a logon struts action
> (that allways fail but...). It is kind of thing to be reuse in a webapp
> so can be provide in a jar... In that uc when you test this kind of jar
> you don't want to include some resources like db access param in the
> final jar artifact.
> 
> I use strutstestcase because some people looks for example on how cactus
> work with it in the user list.
> 
> Nicolas
> 
> >
> > Thanks
> > -Vincent
> >
> >>
> >> Nicolas
> >>
> >>
> >>
> >>
> >>
> >> [EMAIL PROTECTED]
> >> 27/07/2004 20:40
> >>
> >>
> >> Pour :  [EMAIL PROTECTED]
> >> cc :
> >> Objet : [jira] Commented: (CACTUS-132) Allow cactus plugin to
> >> include some
> >> resources
> >>
> >>
> >> The following comment has been added to this issue:
> >>
> >>  Author: Vincent Massol
> >> Created: Tue, 27 Jul 2004 11:40 AM
> >>Body:
> >> Cool. Thanks Nicolas. Could you please also add the associated
> >> changes for
> >> properties.xml, changes.xml and plugin.properties? (and also mabye for
> >> project.xml to add you as a contributor :-))?
> >> -
> >> View this comment:
> >>   http://issues.apache.org/jira/browse/CACTUS-
> >> 132?page=comments#action_36900
> >>
> >> -
> >> 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
> >>
> >>

Re: [jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[Nicolas Chalumeau]

Hi Vincent
Look after for my comment :
Hi Nicolas,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL  PROTECTED]
trelaze.com]
Sent: mercredi 28 juillet 2004 10:37
To: [EMAIL PROTECTED]
Subject: Re: [jira] Commented: (CACTUS-132) Allow cactus plugin to 
include
some resources

Ok pas de probleme. Do you want I modify one of the samples 
application to
illustrate that UC or is there a better way to do some test case in the
maven plugin.

It's hard to write unit tests for maven plugins. I'm not sure what we 
can do
to test your new feature (resource copying). 
I am curious on how to do this so I could try to do it if you want. I 
think that using the plugin:test goal should work to call cactus task in 
the sample applications with the reactor or multiproject. The call could 
be iterate on each type of server... Of course I don't have all the 
servers that cactus support but I could enable a plugin test for tomcat 
and jboss and make it extensible by using a property list of server.

We could of course modify one
of the existing sample so that it does some resource copying but I can't
think of a valid use case that would also be meaningful as an example.
I add a new sample. It is meaningful as it is a logon struts action 
(that allways fail but...). It is kind of thing to be reuse in a webapp 
so can be provide in a jar... In that uc when you test this kind of jar 
you don't want to include some resources like db access param in the 
final jar artifact.

I use strutstestcase because some people looks for example on how cactus 
work with it in the user list.

Nicolas
Thanks
-Vincent
Nicolas


[EMAIL PROTECTED]
27/07/2004 20:40
Pour :  [EMAIL PROTECTED]
cc :
Objet : [jira] Commented: (CACTUS-132) Allow cactus plugin to
include some
resources
The following comment has been added to this issue:
 Author: Vincent Massol
Created: Tue, 27 Jul 2004 11:40 AM
   Body:
Cool. Thanks Nicolas. Could you please also add the associated 
changes for
properties.xml, changes.xml and plugin.properties? (and also mabye for
project.xml to add you as a contributor :-))?
-
View this comment:
  http://issues.apache.org/jira/browse/CACTUS-
132?page=comments#action_36900

-
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: Unassigned
   Priority: Minor
Project: Cactus
 Components:
 Maven Integration
   Assignee:
   Reporter: Nicolas Chalumeau
Created: Tue, 20 Jul 2004 5:18 AM
Updated: Tue, 27 Jul 2004 11:40 AM
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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Wed, 28 Jul 2004 10:29 AM
Changes:
 Attachment changed to properties.xml.diff
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Wed, 28 Jul 2004 10:29 AM

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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Wed, 28 Jul 2004 10:27 AM
Changes:
 Attachment changed to project.xml.diff
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Wed, 28 Jul 2004 10:27 AM

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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Wed, 28 Jul 2004 10:27 AM
Changes:
 Attachment changed to plugin.properties.diff
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Wed, 28 Jul 2004 10:27 AM

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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Wed, 28 Jul 2004 10:26 AM
Changes:
 Attachment changed to changes.xml.diff
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Wed, 28 Jul 2004 10:26 AM

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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Wed, 28 Jul 2004 8:32 AM
Comment:
Here is a sample application that use strutstestcase. This example shows how to test a 
jar who contains struts action and need some file in the webapp classpath.

I will attach other files toonight
Changes:
 Attachment changed to webjar.zip
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Wed, 28 Jul 2004 8:32 AM

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]

[jira] Updated: (CACTUS-132) Allow cactus plugin to include some resources

[cactus-dev]

The following issue has been updated:

Updater: Nicolas Chalumeau (mailto:[EMAIL PROTECTED])
   Date: Tue, 20 Jul 2004 11:32 AM
Comment:
Add a patch.
Changes:
 Attachment changed to plugin.jelly.diff
-
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: Unassigned
   Priority: Minor

Project: Cactus
 Components: 
 Maven Integration

   Assignee: 
   Reporter: Nicolas Chalumeau

Created: Tue, 20 Jul 2004 5:18 AM
Updated: Tue, 20 Jul 2004 11:32 AM

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]