Brian's Enterprise Blog - Responses

Re: How to share resources across projects in Maven

Brian Fox — Tue, 12 Aug 2008 02:22:34 GMT

The eclipse plugin executes the build up to generate-resources, and this can cause problems with dependency:copy/unpack as you mentioned. One solution is to use dependency:unpack-dependencies and some of the parameters to get only the one you want. Another workaround is to bind the plugin to a phase later than generate-resources...this will be easiest if you aren't trying to filter with the resources plugin at the same time.

An even better approach is to use M2eclipse

Re: How to share resources across projects in Maven

Sébastien Moreno — Tue, 05 Aug 2008 16:47:54 GMT

Hi,
this solution seems to work with common work.
But using the eclipse:eclipse plugin produce a new resource folder for eclipse ".classpath". An error can occure when doing a "clean" because the "target" do not exists anymore.

The solution could be to use a specific profile to build the jar with the filtered resourses to include.
But I think that the remote-resources plugin is easier to use in these case.
What do you think?

Re: Maven 2.0.10 Release Candidate Process started

Geoff — Fri, 25 Jul 2008 10:23:58 GMT

Excellent. Thanks for the immediate response.