[ https://issues.jboss.org/browse/JBIDE-15944?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15944: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.1.CR1) Priority: Major (was: Blocker) I remember recently commenting on an issue very similar to this. This issue is not a blocker. It is not a typical use case to modify the initial launch classpath of a server. All JBoss servers ever created have historically had ways of managing systems and subsystems, and specific folders to put additional libraries in to ensure they were automatically loaded. There were very few, if not zero, use cases of manually adding jars to the initial startup classpath. There *is* a bug here, though, in that the displayed value seems incorrect, but this is not a blocker because the server still launches properly. I believe what's happening here, though, is that hte displayed value is an eclipse "classpath container" path. -- 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