[jboss-jira] [JBoss JIRA] (WFLY-1026) Require method to determine best-guess classpath for projects targeted to non-running server
Brian Stansberry (Jira)
issues at jboss.org
Fri Jan 25 07:43:00 EST 2019
[ https://issues.jboss.org/browse/WFLY-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry resolved WFLY-1026.
------------------------------------
Assignee: Brian Stansberry (was: Jason Greene)
Resolution: Won't Do
I don't see us going beyond providing the https://github.com/wildfly/boms boms for each release.
> 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: Brian Stansberry
> 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 was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list