Rod,
what steps do you go through to get the WTP project deployed with maven
filtering?
Tomcat in Eclipse is reading the classpath OK and is pointing at the
unfiltered web resources in my project, so it falls over as soon as it
sees the place holders such as ${root.context} or ${db.connection}.
Adam
Adam Hardy wrote:
Aha. So it works with the maven-eclipse-plugin. Great. It's been a while
since I used that, I transferred over to the Eclipse mavenide plugin
some time ago, it has several advantages over the other - but they're
peripheral really.
I'll try it out tomorrow.
Rod Coffin on 05/10/06 22:00, wrote:
I do this frequently using the Maven eclipse plugin. This plugin will
generate the necessary Eclipse project files from your Maven
metadata. You
can find information on the plugin at:
http://maven.apache.org/plugins/maven-eclipse-plugin/. You will need to
specify the version of WTP that you are using. For example:
"mvn eclipse:eclipse -Dwtpversion=1.5"
Also, you'll want to either create a M2_REPO classpath variable
yourself or
have the plugin do it for you by executing the eclipse:add-maven-repo
goal.
On 10/5/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
I'm trying out the Eclipse Web Tools Platform (WTP) to see what it
offers in terms of the development cycle, and I'm trying to configure a
maven-ised 'dynamic web' project.
I have tomcat configured in Eclipse, and I have associated the maven
project with tomcat, but trying to start it proves that Eclipse hasn't
added the Maven dependencies to the project's classpath.
I cannot see any way to do this and I think I must do it manually in the
config files in my project, but I haven't found any reference about what
files or attributes to edit.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
