I disabled maven-eclipse-plugin configuration, and it works correctly, no errors shown and the package is correctly deployed with WTP!! :)
Thanks a lot Fred for your help (and the entire M2eclipse community), I've never got so far in my maven / j2ee / wtp integration! The poms are very clean, and I do not need extra configurations inside Eclipse. Regards! Juan Ignacio. On Mon, Oct 20, 2008 at 11:33 AM, Fred Bricon <[EMAIL PROTECTED]> wrote: > Can you try again after disabling maven-eclipse-plugin (Ultimately you won't > need it with m2eclipse)? > I imagine you configured it in your parent pom. I suppose it must be > triggered by the process-resources goal defined in the project(s) > properties. > > regards, > > Fred Bricon. > > On Mon, Oct 20, 2008 at 4:23 PM, Juan Ignacio Garzón > <[EMAIL PROTECTED]> wrote: >> >> Thanks fred a lot for your tips!! >> I'm using m2eclipse 0.9.7.20081017-1836 from the dev update site. >> >> I cleaned everything (eclipse .project files, .settings, etc). I >> imported everything using "Import -> Maven projects". I'm getting an >> error: >> "An internal error occurred during: "Importing Maven projects". >> loader constraint violation: when resolving method >> >> "org.codehaus.plexus.util.xml.Xpp3DomWriter.write(Lorg/codehaus/plexus/util/xml/XMLWriter;Lorg/codehaus/plexus/util/xml/Xpp3Dom;)V" >> the class loader (instance of >> org/codehaus/plexus/classworlds/realm/ClassRealm) of the current >> class, >> org/apache/maven/plugin/eclipse/writers/wtp/EclipseWtpApplicationXMLWriter, >> and the class loader (instance of >> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved >> class, org/codehaus/plexus/util/xml/Xpp3DomWriter, have different >> Class objects for the type org/codehaus/plexus/util/xml/XMLWriter used >> in the signature" >> >> Im already noticed that this is a known bug >> (http://jira.codehaus.org/browse/MNG-3668) >> >> After that, the EAR project has no support for WTP (no J2ee facets), >> so I cannot reproduce your steps posted in >> http://jira.codehaus.org/browse/MNGECLIPSE-688. This only happens >> with the EAR project, the EJB and the WAR project seem to be right >> with correct facets. >> After that i deleted all eclipse files from the EAR project and >> regenerated them using mvn eclipse:m2eclipse. I manually changed the >> jst.ear facet to 5.0 (it was generated for 1.4, don't know why). >> >> Now the project is deployed correctly, the only problem is that I have >> an extra folder in the package called "WEB-INF" with a lib directory >> with all my libs. (Its the same that is deployed inside the war). >> >> If there is something I can do to help with these problems, ask me please. >> >> Thanks for your help!! >> >> On Mon, Oct 20, 2008 at 9:56 AM, Fred Bricon <[EMAIL PROTECTED]> wrote: >> > >> > Ola Juan, >> > >> > A few things to check : >> > - which version of m2eclipse are you using? I recommend the latest >> > stable dev build (0.9.7.x) >> > - did you generate eclipse config files beforehand (mvn eclipse:eclipse >> > or mvn eclipse:m2eclipse) ? Generated config is not supported by m2eclipse >> > WTP integration. >> > - Have you tried to update maven project configuration (right click on >> > the project > maven > update project configuration) : that should update >> > your .settings/org.eclipse.wst.common.component >> > - The default ear source directory is src\main\application (where you'll >> > find META-INF\application.xml). You can override it by setting >> > <earSourceDirectory> in maven-ear-plugin config. >> > - Due to a bug in WTP, jar deployment is messy. I recommend using JBoss >> > Tools to deploy ears to JBoss AS (more info here : >> > http://jira.codehaus.org/browse/MNGECLIPSE-688?focusedCommentId=148744#action_148744) >> > - FYI, specific module configuration in maven-ear-config is not >> > supported yet. From your pom.xml, only the context root setting is needed. >> > When different from the war artifactId, you should manually configure it in >> > the web project (right click on the project > properties > Web project >> > settings) >> > >> > Let me know if it helps. >> > >> > regards, >> > >> > Fred Bricon. >> > >> > >> > On Mon, Oct 20, 2008 at 2:26 PM, Juan Ignacio Garzón >> > <[EMAIL PROTECTED]> wrote: >> >> >> >> I have this pom: >> >> >> >> <project> >> >> <modelVersion>4.0.0</modelVersion> >> >> <groupId>myproject.server</groupId> >> >> <artifactId>ear</artifactId> >> >> <packaging>ear</packaging> >> >> <version>1.0</version> >> >> <name>myproject EAR</name> >> >> <parent> >> >> <groupId>myproject</groupId> >> >> <artifactId>server</artifactId> >> >> <version>1.0</version> >> >> </parent> >> >> <dependencies> >> >> <dependency> >> >> <groupId>myproject.server</groupId> >> >> <artifactId>ejbs</artifactId> >> >> <type>ejb</type> >> >> <version>1.0</version> >> >> </dependency> >> >> <dependency> >> >> <groupId>myproject.server.servlets</groupId> >> >> <artifactId>website</artifactId> >> >> <type>war</type> >> >> <version>1.0</version> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.jboss.seam</groupId> >> >> <artifactId>jboss-seam</artifactId> >> >> <version>2.0.2.GA</version> >> >> <type>ejb</type> >> >> </dependency> >> >> </dependencies> >> >> <build> >> >> <plugins> >> >> <plugin> >> >> >> >> <artifactId>maven-ear-plugin</artifactId> >> >> <configuration> >> >> <jboss> >> >> <version>4.2</version> >> >> >> >> <loader-repository>seam.jboss.org:loader=servlet-1.0</loader-repository> >> >> </jboss> >> >> <archive> >> >> <manifest> >> >> >> >> <addClasspath>true</addClasspath> >> >> </manifest> >> >> </archive> >> >> <modules> >> >> <ejbModule> >> >> >> >> <groupId>myproject.server</groupId> >> >> >> >> <artifactId>ejbs</artifactId> >> >> </ejbModule> >> >> <ejbModule> >> >> >> >> <groupId>org.jboss.seam</groupId> >> >> >> >> <artifactId>jboss-seam</artifactId> >> >> >> >> <bundleFileName>jboss-seam-2.0.2.GA.jar</bundleFileName> >> >> </ejbModule> >> >> <webModule> >> >> >> >> <groupId>myproject.server.servlets</groupId> >> >> >> >> <artifactId>website</artifactId> >> >> >> >> <contextRoot>/myproject</contextRoot> >> >> </webModule> >> >> </modules> >> >> <version>5</version> >> >> </configuration> >> >> </plugin> >> >> </plugins> >> >> </build> >> >> </project> >> >> >> >> When I publish it to JBoss using WTP, the ear has this files: >> >> >> >> - META-INF >> >> - application.xml (Empty) >> >> -myproject-ejbs-1.0.jar (Correct) >> >> -myproject-website-1.0.war (Correct) >> >> >> >> The jboss-seam jar and its dependencies are not beying deployed, am I >> >> missing something? The application.xml generated by maven-ear-plugin >> >> is ok, the problem is the one generated by eclipse. >> >> >> >> Here is the .settings/org.eclipse.jdt.core.prefs: >> >> #Sun Oct 19 00:54:09 ART 2008 >> >> org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5 >> >> eclipse.preferences.version=1 >> >> org.eclipse.jdt.core.compiler.source=1.5 >> >> org.eclipse.jdt.core.compiler.compliance=1.5 >> >> >> >> Here is the .settings/org.eclipse.wst.common.component: >> >> <project-modules id="moduleCoreId" project-version="2.0"> >> >> <wb-module deploy-name="myproject-ear-1.0"> >> >> <wb-resource deploy-path="/" source-path="target/eclipseEar"/> >> >> </wb-module> >> >> </project-modules> >> >> >> >> Here is the .settings/org.eclipse.wst.common.project.facet.core.xml: >> >> <faceted-project> >> >> <fixed facet="jst.ear"/> >> >> <installed facet="jst.ear" version="5.0"/> >> >> </faceted-project> >> >> >> >> I'm using WTP 3.0.2 and Eclipse 3.4. >> >> >> >> Thanks a lot I'm trying to make this work since a week! >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe from this list, please visit: >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> > >> > >> > >> > -- >> > GMail rox! >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > > -- > GMail rox! > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
