ChrisGWarp wrote:
So, your "update project configuration" is similar in function to the
maven-eclipse-plugin code? In that it creates the necessary eclipse
.settings files/.project/.classpath files based upon the contents of the
POM?
I've put a good deal of working in getting the POM to work with the
maven-eclipse-plugin. Why not, use some of their code? It seems to me that
it would solve what you want?
But that is is another way of saying: I don't understand what you are trying
to achieve with the m2eclipse plugin where there are others that do
_similar_ features. Granted your ability to edit the POM and concept of the
Maven Managed Dependencies classpath container (which I think is a brilliant
idea!)
Like I tried to explain in another thread, we basically extend Maven
Managed Dependencies to work with WTP projects. Right now this is
implemented for WAR projects only, but we plan to eventually support
other J2EE project types. Support for EJB and EAR projects should be
relatively straightforward to implement but currently it is not high on
our priority list (not too many people have asked for it so far, to be
honest).
-Chris
Eugene Kuleshov wrote:
Henri,
Please note that you may need to run "update project configuration" to
make things work between Maven and other Eclipse tools, such as WTP.
Also note that WTP configurator in m2eclipse currently does not support
EAR projects [1].
If someone want to implement EAR support in WTP project configurator,
please let us know. We will be happy to give you pointers that would
help you started.
regards,
Eugene
[1]
http://tinyurl.com/3kwbd5#Extensibleprojectconfigurationframework-WTPintegration
Henri Gomez wrote:
More informations.
I see in the settings, the following files (added by a co worker) some
times ago :
org.eclipse.wst.common.component :
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="slib-erable-framework" project-version="1.5.0">
<wb-module deploy-name="slib-erable-framework">
<wb-resource deploy-path="/" source-path="/src/main/java"/>
<wb-resource deploy-path="/" source-path="/.apt_generated"/>
<wb-resource deploy-path="/" source-path="/src/main/resources"/>
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/resource/slib-jutils/slib-jutils">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
org.eclipse.wst.common.project.facet.core.xml :
<?xml version="1.0" encoding="UTF-8"?>
<faceted-project>
<fixed facet="jst.java"/>
<fixed facet="jst.utility"/>
<installed facet="jst.java" version="5.0"/>
<installed facet="jst.utility" version="1.0"/>
</faceted-project>
2008/6/10 Henri Gomez <[EMAIL PROTECTED]>:
After upgrading to 0.9.4 (from 0.9.3), I notice some projects failed
since they depends on others projects, also in the workspace.
I found these projets in Maven Dependencies and EAR.
It's strange since my project is just plain Java project :
Here is its .classpath :
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="src" path=".apt_generated"/>
<classpathentry kind="src" path="src/main/resources"/>
<classpathentry kind="src" output="target/test-classes"
path="src/test/java"/>
<classpathentry kind="src" output="target/test-classes"
path="src/test/resources"/>
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
<classpathentry kind="con"
path="org.eclipse.jst.j2ee.internal.module.container"/>
<classpathentry kind="output" path="build/classes"/>
</classpath>
Regards
---------------------------------------------------------------------
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
