This is an anti-pattern in Maven usage.
Modules should be self-contained. If you must include content from
another module, then you should depend on the Jar just like any other
artifact and use various plugins to unpack the files you need into a
specific area in your project etc. You should not use ".." or
hard-code paths etc to access content which belongs to other modules
(parents or children).
Wayne
On 4/25/08, Lachlan Deck <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> If I have the following, all's fine... i.e., the resources are filtered and
> found in the build output.
> <resource>
> <targetPath>Resources</targetPath>
> <filtering>true</filtering>
> <directory>../src/main/resources</directory>
> </resource>
>
> However the following produces no results...
> <resource>
> <targetPath>Resources</targetPath>
> <filtering>true</filtering>
>
> <directory>${project.parent.basedir}/src/main/resources</directory>
> </resource>
>
> What properties are available for referencing the parent?
> Thanks.
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
>
> ---------------------------------------------------------------------
> 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]
