If it is causing confusion I would be happy to change it - please raise an
issue in Jira: http://issues.appfuse.org/browse/APF
Mike
On 15/04/2008, Chad Chen <[EMAIL PROTECTED]> wrote:
>
> Thanks for the reply.
>
> If my current project A has a dependency on B, whose WEB-INF/classes does
> the fo
Thanks for the reply.
If my current project A has a dependency on B, whose WEB-INF/classes
does the following sentence refer to?
---
warpathExcludesStringThe filter that determines the resources, from
the "dependent" war's WEB-INF/classes directory, to exclude from the
I think a better word would be "target" war if that's what is being
built here...?
On Tue, Apr 15, 2008 at 11:04 AM, Matt Raible <[EMAIL PROTECTED]> wrote:
> We use dependent because it seems to work best when describing a
> dependency - which is what the war is in your pom.xml.
>
> Matt
>
>
>
>
We use dependent because it seems to work best when describing a
dependency - which is what the war is in your pom.xml.
Matt
On Tue, Apr 15, 2008 at 11:47 AM, Chad Chen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> When I read the following documentation at the following URL:
>
> http://static.appfuse.o
Hi,
When I read the following documentation at the following URL:
http://static.appfuse.org/maven-warpath-plugin/add-classes-mojo.html
I am confused by the word "dependent" in the following context:
---
Optional Parameters
warpathExcludesStringThe filter
