[ https://jira.jboss.org/browse/JBIDE-6767?page=com.atlassian.jira.plugin.s... ] Snjezana Peco resolved JBIDE-6767. ---------------------------------- Fix Version/s: 3.2.0.M2 (was: 3.2.x) Resolution: Done There is a problem with JBoss (or WTP) deployer. m2eclipse-wtp creates the following component.xml file : ... <dependent-module archiveName="/lib/jbpm-jpdl-3.2.2.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/org/jbpm/jbpm-jpdl/3.2.2/jbpm-jpdl-3.2.2.jar"> <dependency-type>uses</dependency-type> </dependent-module> <dependent-module archiveName="/lib/drools-api-5.0.1.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/org/drools/drools-api/5.0.1/drools-api-5.0.1.jar"> <dependency-type>uses</dependency-type> </dependent-module> <dependent-module archiveName="/lib/richfaces-api-3.3.1.GA.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/org/richfaces/framework/richfaces-api/3.3.1.GA/richfaces-api-3.3.1.GA.jar"> <dependency-type>uses</dependency-type> </dependent-module> <dependent-module archiveName="/lib/mvel2-2.0.10.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/org/mvel/mvel2/2.0.10/mvel2-2.0.10.jar"> <dependency-type>uses</dependency-type> </dependent-module> ... The jbpm-jpdl-3.2.2.jar, drools-api-5.0.1.jar, richfaces-api-3.3.1.GA.jar... are deployed correctly to the EAR's lib directory, but mvel2-2.0.10.jar is deployed to the EAR's lib/lib directory. The problem is that manifest in mvel2-2.0.10.jar contains the Main-Class: declaration; WTP treats such jars as an application client and deploys them incorrectly. The problem can be reproduced as follows: - disable the JBoss Maven Seam Configurator - create a mavenized Seam EAR Project - publish the project or - disable the JBoss Maven Seam Configurator - create a mavenized Seam EAR Project - add <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam-pdf</artifactId> </dependency> to the EAR's pom.xml - publish the project jboss-seam-pdf includes itext.jar which also contains the Main-Class declaration. Because of that, itext.jar will be deployed to the lib/lib directory. I have made a workaround within the JBoss Maven Seam Configurator that changes mvel deployment in component.xml to the following: ... <dependent-module archiveName="mvel2-2.0.10.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/org/mvel/mvel2/2.0.10/mvel2-2.0.10.jar"> <dependency-type>uses</dependency-type> </dependent-module> ... The workaround fixes the problem when creating a mavenized Seam Web project, but doesn't fix it if the user adds a jar with the Main-Class declaration in the Ear's pom.xml (itext.jar, for instance). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6767?page=com.atlassian.jira.plugin.s... ] John Franey commented on JBIDE-6767: ------------------------------------ I dug a bit further. Although, the deploy location of mvel may be a problem, it is not the problem in my forum post, referenced in the summary of this bug. My posting says that an error is generated when deploying a seam project created by jboss tools using the maven integration. I've been able to reproduce the problem easily. The root cause is the application.xml file that is created during the project creation. It contains jboss-seam jar file twice. Editing the file in eclipse editor and removing one of the ejb entries fixes the problem. Here is application.xml as it appears immediately after creating seam project with maven integration: <?xml version="1.0" encoding="UTF-8"?> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.x... xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>trumpet-ear</display-name> <module> <ejb>jboss-seam.jar</ejb> </module> <module> <web> <web-uri>trumpet.war</web-uri> <context-root>/trumpet</context-root> </web> </module> <module> <ejb>trumpet-ejb.jar</ejb> </module> <module> <ejb>/jboss-seam-2.2.0.GA.jar</ejb> </module> <library-directory>lib</library-directory> </application> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6767?page=com.atlassian.jira.plugin.s... ] Snjezana Peco commented on JBIDE-6767: -------------------------------------- The problem related to mvel.jar is also fixed by this jira. If you use a newer JBoss Tools, you won't need any workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6767?page=com.atlassian.jira.plugin.s... ] Libor Zoubek closed JBIDE-6767. ------------------------------- You're right. verified on JBT 3.2.0 M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira