[jboss-jira] [JBoss JIRA] (WFLY-1026) Require method to determine best-guess classpath for projects targeted to non-running server

Rob Stryker (JIRA) jira-events at lists.jboss.org
Mon May 6 05:32:53 EDT 2013


     [ https://issues.jboss.org/browse/WFLY-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated WFLY-1026:
------------------------------

    Priority: Critical  (was: Major)

    
> Require method to determine best-guess classpath for projects targeted to non-running server
> --------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1026
>                 URL: https://issues.jboss.org/browse/WFLY-1026
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Server
>            Reporter: Rob Stryker
>            Assignee: Jason Greene
>            Priority: Critical
>
> JBossTools requires some method to discover from a non-running server which jars should be added to a project as exposed for clients (the project) to use. This should be a best-guess and does not need to be complete, but it's better if there is a way to determine which jars are public or private. 
> I'm not sure if this would be best addressed by jboss-modules, or some type of marker files (which it could be argued is a bad solution and we have too many such workarounds), or what. 
> Previous possible solutions introspected the xml files for each module to determine what jars / packages were public / private, but this was deemed unacceptable for reaching into a modules folder by ourselves. 
> Before that, we simply hard-coded which jars or folders to add for each app server version. 
> Requiring a running server violates our use case. Speed is of a high importance, and so therefore launching a new VM against a main class in jboss-modules is also not a great solution. 

--
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


More information about the jboss-jira mailing list