jira-importer commented on issue #52: URL: https://github.com/apache/maven-ejb-plugin/issues/52#issuecomment-2879259075
**[tinne](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tinne)** commented As a partial workaround, I found I can add server-only dependencies as optional dependencies to the ejb module. Giving them as mandatory dependencies for any ear module containing the server-ear, the dependencies (and also transitive dependencies, as mentioned above) are worked out fine. The manifest.mf however, having the classpath added (\<configuration>\<archive> \<manifest>\<addClasspath>true\</addClasspath> \</manifest>\</archive>\</configuration>) still has all server library entries referenced which are not available in client.jar packages (Which is, at least, ugly, but should not lead to trouble except when ill-naming dependency jars or depending on different dependency jar versions in different parts of the system.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
