[jbosstools-issues] [JBoss JIRA] (JBIDE-17236) Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute
Martin Malina (JIRA)
issues at jboss.org
Wed Jun 18 10:29:24 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Malina closed JBIDE-17236.
---------------------------------
OK, so Rob gave me instructions how to try this:
1. Create a web project
2. Open the manifest.mf
3. Add a Dependencies: attribute, e.g.
Dependencies: nu.xom
4. New entry should appear in the project's classpath (Project -> Properties -> Java Build Path -> Libraries -> runtime)
And it worked!
Verified in JBDS 8.0.0.Beta2d
> Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-17236
> URL: https://issues.jboss.org/browse/JBIDE-17236
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
>
> Projects that have a manifest.mf which declares Dependencies as per https://docs.jboss.org/author/display/MODULES/Manifest+module+information should have those dependent modules added to the classpath.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jbosstools-issues
mailing list