Okay... I got it to work. Great! I didn't realize that you should run
eclipse:eclipse every time a dependency is added to let it update the
.component file.
The only problem I have now, is when I use the m2eclipse plugin for
eclipse. After enabling the Maven2 nature for the project it
Fabrizio Giustina wrote:
On 5/10/06, Matthijs Wensveen [EMAIL PROTECTED] wrote:
When I try to run the project on a server from within eclipse, the
dependencies that would normally be in WEB-INF/lib are not deployed on
the server.
They should be deployed, probably you are using a buggy version
Using
mvn -Dwtpversion=1.0 eclipse:eclipse works for me to get them added
when deploying within Eclipse using WTP 1.0.2 Eclipse 3.1.2.
The applicable file that eclipse:eclipse generates is .settings/.component
Make sure the dependencies that should be bundled are described in
that file
Hi,
I have a maven project as an eclipse WTP project. I created the project
with maven-archetype-webapp and then ran the maven eclipse plugin to
convert it to a wtp 1.0 project. This works. I also use the mergere
m2eclipse plugin for eclipse. This also works (hurray!).
When I try to run the
On 5/10/06, Matthijs Wensveen [EMAIL PROTECTED] wrote:
When I try to run the project on a server from within eclipse, the
dependencies that would normally be in WEB-INF/lib are not deployed on
the server.
They should be deployed, probably you are using a buggy version of
WTP. WTP r7 shipped
Fabrizio Giustina wrote:
On 5/10/06, Matthijs Wensveen [EMAIL PROTECTED] wrote:
When I try to run the project on a server from within eclipse, the
dependencies that would normally be in WEB-INF/lib are not deployed on
the server.
They should be deployed, probably you are using a buggy version
