[ https://issues.jboss.org/browse/JBIDE-13139?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13139: ------------------------------------- It does not currently use module system. We have the first one (a way to add a server lib to the classpath for a server, or for all projects targeted to a server type). We do not have the second one (based on modules). And no, it is not able to be tweaked per project, and never will be. Per-server, maybe. Per-project? No. Making this configurable per project would provide no benefit, as the user could then just as simply go and add the jars to the project directly, rather than configuring that server1 for project-A should add jar-X. Why not just go add jar-X manually to the project-A? It'd be about the same number of UI steps, or even fewer. When adding directly to a project, you right-click the project, properties, go to build path, and add the jar. If you wanted to customize this via the current UI (and extend it to allow customizations per project), then you'd need to go to windows -> properties -> Runtime Environment -> Default classpaths -> Some extra page to select the server type -> Some extra page to select a project -> Add a jar. And then you're adding more UI elements, more hidden settings, and more places for people to get confused. It could conceivably be done via the classpath container directly, passing settings into the container in some fashion... though exactly what settings to pass in is beyond me. Honestly, if you have a project-specific jar you want to add, it belongs being added via build path... not configuring the jboss-eap-6.0 runtinme classpath per-project classpath customizations. But I'm leaving this bug open to target the possibility of introspecting the standalone.xml for a modules configuration. > Improve libs import for EAP 6 > ----------------------------- > > Key: JBIDE-13139 > URL: https://issues.jboss.org/browse/JBIDE-13139 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 3.3.0.Final > Environment: JBDS 4.x > EAP 6/AS 7 > Reporter: William Siqueira > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept. > The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira