jira-importer commented on issue #181: URL: https://github.com/apache/maven-war-plugin/issues/181#issuecomment-2967848323
**[Hockchai Lim](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hockchailim)** commented This WAR module is really a EJB module. I followed Tomee's suggestion on packaging a EJB in WAR file (http://tomee.apache.org/deploying-in-tomee.html). So, this WAR module is really a EJB server app. All the dependencies declared in this module are for this module only. For all its ejb client modules, I would do below to include the ejb client jar: \<dependency> \<groupId>MyEJBGroupID\</groupId> \<artifactId>MyEJBArtifactId\</artifactId> \<version>1.0\</version> \<type>ejb-client\</type> \</dependency> ejb client module does not need server's transitive dependencies, and hence the optional attribute are added to them. The purpose of optional dependency is to allow the author to declare dependency for a project/module that is strictly for that project/module only. The WAR plugin not including optional dependency in WEB-INF/lib for that project/module seems to be breaking the purpose of this attribute. -- 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
