[
https://issues.jboss.org/browse/WFCORE-3765?page=com.atlassian.jira.plugi...
]
James Perkins reopened WFCORE-3765:
-----------------------------------
Reopening because {{org.jboss.msc:jboss-msc}} needs to be a runtime dependency. The
s{{org.jboss.msc.service.ServiceContainer}} is used as an instance variable for the
standalone server and the host controller. This requires that MSC be on the flat class
path.
Make the embedded module maven deps very clear
----------------------------------------------
Key: WFCORE-3765
URL:
https://issues.jboss.org/browse/WFCORE-3765
Project: WildFly Core
Issue Type: Task
Components: Embedded
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 5.0.0.Alpha5
The embedded module pom should be as precise as possible about dependencies so it is
crystal clear what needs to be on the embedding app's classpath.
1) Any dependency should have an exclude to exclude all transitives. So all deps should
have to be declared in order to compile.
2) Any dependency that at runtime is only used via the embedded process side modular
classloader should use scope 'provided'. These should also be grouped together in
the pom. At runtime these dependencies do not need to be available to the embedding
app's classloader; the embedding app creates a modular classloader configured with an
appropriate module path and these deps are loaded that way. The maven 'provided'
notion basically aligns with this concept.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)