[
https://issues.jboss.org/browse/WFLY-1160?page=com.atlassian.jira.plugin....
]
James Livingston commented on WFLY-1160:
----------------------------------------
To have "common libraries" directory would require deciding what modules were
visible to it, since unlike earlier versions where there was a main classloader for the
server, there is not any more.
Regardless of the choice of dependencies, I suspect many people would want to be able to
configure it. At that point, it doesn't seem to me that it would be any different from
a normal module added to the EE subsystem global modules, apart from the "include all
jars in the directory" part, which could be done if MODULES-99 was implemented.
Adding config files to AS7 is inconvenient.
-------------------------------------------
Key: WFLY-1160
URL:
https://issues.jboss.org/browse/WFLY-1160
Project: WildFly
Issue Type: Feature Request
Components: Class Loading
Environment: All
Reporter: Paul Hinds
Assignee: David Lloyd
Priority: Minor
Labels: regression
This page
https://community.jboss.org/wiki/HowToPutAnExternalFileInTheClasspath details
how to put a directory on the AS7 classpath which is inconvenient and could easily be done
by default.
If AS7 out of the box came with /standalone/classes or /standalone/conf (conf would
introduce a bit of backwards compatability) and perhaps /standalone/lib/*.jar added to the
classpath it would be as good as previous JBoss versions.
This could be implemented as a module as in the above documents and automatically added
to classpaths if the dirs exists in the same way other modules are automatically added to
the CP if certain criteria are met.
Ideally is should be possible to make these symlinks on win7 and nix. Since it is natural
to put config in /etc per Linux file system standards.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)