[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-282) Maven pom.xml backed project libraries instead of hardcoded classpath containers

Maven pom.xml backed project libraries instead of hardcoded classpath containers -------------------------------------------------------------------------------- Key: JBIDE-282 URL: http://jira.jboss.com/jira/browse/JBIDE-282 Project: JBoss Tools Issue Type: Feature Request Reporter: Tuomas Kiviaho Priority: Optional When usign a IDE plugin project creation there usually will come couple of hardcoded eclipse libraries a.k.a classpath containers that most likely will be referenced by the project. If the JBoss IDE with all the neccessary plugins are not installed, all of the project dependencies behind plugin spesific classpath will cause project not to compile. In this scenario it's quite hard to backtrack the original packages. When IDE evolves and dependencies change, temporary plugin installation doesn't fix the problem, if original IDE version is not known. Therefore SCM requires additional documentation over how to resolve depencencies. I have noticed that the next generation JBoss build system package dependency mechanism will be Maven. Instead of hadrcoded... new IPath[] { new Path("jboss-aop-jdk50.jar"), new Path("jboss-common.jar"), new Path("qdox.jar"), new Path("concurrent.jar"), new Path("trove.jar"), new Path("javassist.jar"), new Path("jboss-aspect-library-jdk50.jar"), new Path("pluggable-instrumentor.jar") }; ...the project depencencies could be the same as with original Maven pom.xml of the (JEMS) project against which the plugin is meant. There is a Maven plugin already that makes a virtual eclipse library against the project pom.xml Even without maven plugin installed the depencencies still are self explainatory and there is no need for additional documentation.