[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7470) EAR produced by command line is different from that produced by Tools

[ https://jira.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin.s... ] Snjezana Peco commented on JBIDE-7470: -------------------------------------- There are several issues with this application and they are the following: 1. When creating an application using the Maven 2 command line (I have tested Maven 2.2.1), the application works properly on the JBoss AS 6. I have used AS 6 CR1. When using the Maven 3 command line or m2eclipse 0.12 embedded, the application doesn't work on AS 6 CR1.The problem is that Maven 3 adds the commons-logging library to WEB-INF/lib which causes the server to throw "Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed." exception. commons-logging is a transitive dependency (hibernate-core>ehcache>commons-logging). I think this is a bug in Maven 3. The solution would be to exclude commons-logging 2. Photoalbum uses resource filtering in the components.properties and components.xml files. That feature doesn't work in m2eclipse. The solution - removing resource filtering. 3. Photoalbum defines the artifactId element of ear,ejb and web projects using the ${projectName} property. m2eclipse imports projects based on artifactId. The projects are named ${projectName}-ear /ejb/web. JBT/WTP deploys such projects as ${projectName}-ear.ear that JBoss AS doesn't deploy correctly (the application name and repository loader are different) The solution would be to define the projects with fixed names (photoalbum, photoalbum-ejb, photoalbum-ear , photoalbum-web) 4. EAR's finalName is defined as $projectName-ear-$versionName}. JBT/WTP/m2eclipse ignores deployName and, as a result, the project is always deployed with the name <EclipseProjectName>.ear (photoalbum-ear.ear). The solution is to define EAR's final name as photoalbum-ear We have a project example that include all these fixes except the fix for the problem 1. It uses Richfaces 3.3.1 and Seam 2.2.0. Max, I could add the fixes to the photoalbum application or upgrade our project example to Richfaces 3.3.3 and Seam 2.2.1.CR2. WDYT? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira