maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)

I have attached the relevant POM with correct indentation

I created a patch with a workaround. Apply the patch and create your own version of the plugin.

Thank you. It works like a charm. Will this patch get eventually into official sources?

the configuration is not the place to do this.

If I understand correctly, you want to have filtered resources copied to a different location. That is what targetPath is for:

<resource>
<directory>src/main/properties</directory>
<filtering>true</filtering>
<targetPath>some/path/under/target/classes</targetPath>
</resource>

Brett unfortunatelly you don't. I need to use maven-resources-plugin in generate-resources phase. I do not want src/main/properties as a resource because eclipse would copy unfiltered resources (with @TAGS@) to target/classes. That prevents me from running test cases from under eclipse.

So I just want to process src/main/properties into target/generated-resources (which I make a resource). This way eclipse never deals only with postprocessed resources.

You're right it does not make much sense to use configuration/resources in process-resources phase. Still it is useful for former phases.

Is that explanation enough to drop 'won't fix' ?

ok, we should probably add a new mojo for copying files that will not be packaged.

Example

My discussion on irc with Kenney ended up with the conclusion that something is wrong in plexus configurator because maven-resources-plugin mojo 'resources' field cannot be set from configuration (although it is not read-only). Thus the patch provided is only a workaround.

I guess the expression wins if not null.

I must chime in here because the root cause of this issue report has caused me extreme headaches. In my mind, and everyone sitting around me on the CM team, this is a MAJOR oversight in the resources plugin. Regardless of how it is fixed, it really just needs to be fixed (to get it out there) and then refactored. I will explain my use case and prove how badly we need this patch to go in (otherwise we will forever maintain our own version of this plugin to get our job done).

Our goal is to use profiles to search/replace tokens in the src/deploy/webinf directory to end up in the final package (war file). We do this by setting up a plugin execution to run maven-resources-plugin during the process-resources phase. The snippet is as follows:

<execution>
<id>webinf-resources</id>
<phase>process-resources</phase>
<goals><goal>resources</goal></goals>
<configuration>
<outputDirectory>$

/$

</outputDirectory>
<resources>
<resource>
<targetPath>WEB-INF</targetPath>
<directory>$

/src/deploy/webinf</directory>
<filtering>true</filtering>
</resource>
</resources>
</configuration>
</execution>

In the current version of the plugin, these resources are simply ignored. The plugin must be used because both the output directory and the target path need to be specified (no other combination is possible, trust me, I tried everything). Is there really any reason why the resources configuration node cannot simply be handled in the plugin without major refactorings?

– two months later –

is there now a fix to this problem available? Or another plugin with which you can copy around in your project at wish?

• over a year later -

Any answers to Andreas' questions yet?

Any activity on this issue:

I just ran into this today. Needed to copy/process some resources before the integration phase but impossible to set the resource directory. As suggested there should either:

• be the possibility to specify resources to include
• or a separate mojo that would copy any resource to any directory.

Our work around for the moment, using ANT, not really nice...

IMHO adding a mojo called copy-resources is the best option here.

I just ran into this issue, I was willing to submit a patch but I saw that it was already submitted, any chance to release the patched version of the plugin to the central repository ?

The question is : we call this new mojo copyResources or copy-resources ?
My +1 for copy-resources.
Comments are welcome !
Thanks,
–
Olivier

+1 for copy-resources, that matches the majority of goal names.

Implemented in rev 694813
I leave the issue open until there is more tests and documentation.

Do we have to attach this mojo to phase ?
IHMO no.
But comments are welcome
Thanks!

junits, its and example in site are ok.

Olivier, given that users apparently cannot override the parameter resources from the ResourcesMojo, should we mark it @readonly to hide it from the plugin docs and prevent future confusion?

Good idea !