Brennan,
There is an explicit action that can be invoked at any time after
"dependency management" is enabled. I have to check if "enable
dependency management" is using the same logic, so please verify if
using "update project configuration" produces correct results.
You can also comment on the bug report how in your opinion project
configuration should look like for your test project.
Thanks
Eugene
Spies, Brennan wrote:
Eugene,
It is the "update project" (I assume this happens when you "Enable Dependency
Management") that is causing problems with the existing configuration. I'll file a JIRA.
Brennan Spies
Sr. Programmer Analyst
E. & J. Gallo Winery
No, things don't all go the way they should,
But I know the heart of life is good...
-- John Mayer
-----Original Message-----
From: Eugene Kuleshov [mailto:[email protected]]
Sent: Thursday, February 12, 2009 1:02 PM
To: [email protected]
Subject: Re: [m2eclipse-user] RE: Running web apps with m2eclipse
Brennan,
Generally it is not recommended to manually edit .classpath and other
project configuration files. Instead you should be using Maven / Update
project configuration action. Assuming that your pom.xml is correct, so
"mvn package" command for this project produces the deployable war, the
update project action should configure your projects to work properly
with WTP.
If that is not the case, please submit a bug report and provide test
project and instructions that would allow to reproduce this.
Thanks
Eugene
Spies, Brennan wrote:
OK,
I'll answer my own question. Apparently, the .classpath file was not
correct.
It was:
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
It should have been:
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER">
<attributes>
<attribute name="org.eclipse.jst.component.dependency"
value="/WEB-INF/lib"/>
</attributes>
</classpathentry>
Unfortunately, there's a few other problems. Looks like converting
existing Eclipse-style webapps to m2eclipse is not a good idea.
*From:* Spies, Brennan
*Sent:* Wednesday, February 11, 2009 2:51 PM
*To:* '[email protected]'
*Subject:* Running web apps with m2eclipse
All,
I've got a question about using dependency management when running
Tomcat through the Eclipse launcher and using dependency management
courtesy of m2eclipse. I have two older projects that I converted to
use Maven/m2eclipse, and both are webapps. I kept the same general
folder structure that Eclipse gives you when you create a Dynamic Web
app in Eclipse, and I've simply adjusted the pom.xml to refer to the
appropriate source (src) and output(WebContent/WEB-INF/classes) folders.
When I run these apps on Tomcat through the Eclipse launcher, one
works (i.e. successfully publishes jars to WEB-INF/lib) and the other
one doesn't (java.lang.NoClassDefFoundError: org/apache/log4j/Logger).
I can see the publish/export dependency in the classpath container for
both projects. In the
.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps folder
I can see the jars for the two workspace-resolved projects, but none
of the other declared dependencies.
This is probably not an m2eclipse-specific problem (I can see the same
issue with IvyDE), but I was just wondering if anyone has seen this
issue before.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
