What I was referring to in item no 1 was for a Maven goal to be
automatically executed when WTP is used to launch and publish to a server.
This would be necessary to execute resource filtering for e.g. As for having
Eclipse copying web resources, you can edit the
.settings/org.eclipse.wst.common.component preferences file to include
something like the following:
<wb-resource deploy-path="/WEB-INF/classes"
source-path="src/main/resources"/>
On 8/23/07, Adam Hardy <[EMAIL PROTECTED]> wrote:
>
> Richard Gill on 23/08/07 13:29, wrote:
> > There are 2 areas (that aren't currently supported) that I think need to
> > be supported if the integration with WTP will work:
> >
> > 1. Having WTP execute a Maven goal when launching a server (to do
> > resource filtering for e.g.)
>
> You mean "publish" to a server I think (which can be set as an option to
> occur
> automatically on launching the server - look in preferences/server).
>
> I'm not sure about the mechanics of filtering and its position in the
> maven
> lifecycle. For instance, can java source files be filtered?
>
> I think it's better to get maven to do filtering when eclipse builds the
> project.
>
> IIRC eclipse copies non-java files across to target if they are on the
> build
> path and filtering them by maven at that point is the time to do it.
>
> Might be possible already, it's something I'll have to check out soon
> since I
> need it in my current project, or maybe it's in Jira as a requirement.
>
> However eclipse doesn't copy all the web resources across and so maven
> would
> have to do that itself.
>
>
> Adam
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
