Patrick--
As the <filtering>false</filtering> is defaulting to false so you would
have to override the filtering value to change the output of pom.xml
The doc http://maven.apache.org/guides/getting-started/index.html states
In addition, we had to explicitly state that the resources are located in
the src/main/resources directory.
All of this information was provided as default values previously,
but because the default value for filtering is false,
we had to add this to our pom.xml in order to override that default value
and set filtering to true.
in the provided example:
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
HTH
Martin
----- Original Message -----
From: "Patrick Flynn" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 09, 2008 8:23 PM
Subject: resource filtering and your IDE
Hi everyone,
I think that I must be hitting a google black hole on this one as I can't
find any good solutions to what seems to be an obvious integration concern
between IDEs and maven.
I've been spending far too much time trying to make maven resource
filtering
work well with our teams IDEs (eclipse and intellij 7), but have had very
little success. My main issue is that for fast code then test turnaround
on
our webapp we use the IDE build mechanism to make quick changes to jsps
and
classes and have only those changes placed into our exploded directory
structure during a make. Unfortunately the ides will always copy over
everything in the source path into the classes directory unfiltered. If I
remove the resource directory from the src path and hook in maven
'process-resources' into the make process I get some of what I need but
then
the IDE integration that allows you to autocomplete application.properties
etc no longer works as the files are no longer in the classpath as far as
the IDE is concerned.
I also tried placing filtered resources into their own directory and
targeting them to the resource base directory
i.e. something like this
<resource>
<filtering>true</filtering>
<directory>src/main/filtered-resources</directory>
<targetPath>../../src/main/resources</targetPath>
</resource>
but this seems rather uncool and I find myself cringing at deviating from
the standard directory structure to accomodate tools, having target output
in my src path, and that targetPath is relative to the target classes
output
directory.
I'm guessing that this has been solved already but I'm just not finding
the
solution. Any takers on helping me out with this?
thanks in advance,
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
