Looks like that dependency is mapped from maven to libraries.ent with this config
<dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-server-manager</artifactId> <mapping> <componentId>jboss.server.manager</componentId> </mapping> </dependency>
If you want to add additional jars to the jboss.server.manager.classpath you would just have to map those dependencies to the same componentId. The maven plugin that generates libraries.ent doesn't understand maven transitive dependencies, so it won't automatically figure those out. By default it will just translate groupId to componentId so dependencies with the same groupId (that are not mapped to a different componentId) are combined into one component with the associated properties in libraries.ent.
I suspected that for the groupId but didn't understand mapping would do the same.
So if I need additional jars that don't currently specify mapping, I will have to include their groupId as a mapping additionaly to "jboss.server.manager", right?
What about scope? "jboss.server.manager" is only for tests but its dependencies are not. Can I still pecify scope to server manager and expect it works?
I'll try anyways,
I see how the scope works.
As well I realized that I don't need to have these libraries taken from outside but need these built now. I'll start another thread about it.
Thanks for the help!