[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-1527) Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure

Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure --------------------------------------------------------------------------------------------------- Key: JBIDE-1527 URL: http://jira.jboss.com/jira/browse/JBIDE-1527 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Mehmet Salgar Fix For: 2.1 Hi, my request is Red Hat Studio and Maven 2 related. I think Red Hat Studio should create (or at least give the possibility) for the Jboss Seam projects in a structure that is compatible with a Maven 2 structure. It is undeniable fact that java programmers are moving toward Maven 2 to manage their depenencies (even JBoss http://in.relation.to/Bloggers/Pete, http://www.michaelyuan.com/blog/2007/10/09/jboss-seam-project-setup-with-..., http://www.jroller.com/wesleyhales/, http://jbossportal.blogspot.com/), in this time it is interesting that an IDE that is developed with Red Hat and JBoss is not supporting directory structure of Maven 2. With Beta2, I can create a JBoss Seam project and create necessary pom.xml for the web module to be compatible with Maven 2 but with ejb module it is not possible, because maven-ejb-plugin needs ejb-jar.xml (or anything in META-INF) to be in src/main/resources. It is not possible to configure this for any other directory in maven-ejb-plugin. It is not possible to change the directory structure in RHDS also, it is default ejbModule/META-INF, there must be at least a way to set this to src/main/resources during the project creation. Same is valid for the web project creation, there I can choose the directory but on a flat level, so it can be src, main but not src/main/java or src/main/webapp. As I said little bit more compatablity with Maven 2 or little bit more configurablitiy from RHDS would be nice, it would be really stupid not be able to use Maven 2 while it is not RHDS project structure compatible and it would be also stupid not to be able to use RHDS features while it is Maven 2 project structure incompatible......