Hi
Instructions on how filtering works in the Resources Plugin can be found
on this page:
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
[EMAIL PROTECTED] wrote:
> Hi,
>
>
>
> here is a small story about working with Maven. In my experience of 6 months
> now t
On Friday 05 September 2008 [EMAIL PROTECTED] wrote:
> But for me the
> problem is not only documentation but also a user-friendly design. Take
> the filtering example: For main/resources you have
> main/resources ... And for test/resources you have
> to say
> test/resources ...
> This is redundant
]
Gesendet: Freitag, 5. September 2008 10:40
An: Maven Users List
Betreff: Re: from workaround to workaround 1
After all,
I consider this classical paradigm of "all you need is there, just obstructed
by details all over".
"Filtering did not work" because does filtering for mains
After all,
I consider this classical paradigm of "all you need is there, just obstructed
by details all over".
"Filtering did not work" because does filtering for mainstream, but
Wolfgang needed filtering for "test".
If you know what to look for, this distinction is quite obvious from the docs.
Wolfgang,
For test resources you should use the element, not the
element. The documentation is a bit shallow on this matter.
Asgeir
On Fri, Sep 5, 2008 at 08:46, <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> here is a small story about working with Maven. In my experience of 6
> months now this ha
Hi,
here is a small story about working with Maven. In my experience of 6 months
now this happened very often like this. Maven is very hard to manage, not
intuitive and error messages are incomprehensible or misleading.
The problem: We have 5 Maven projects with sub projects. For test cla
