jira-importer commented on issue #100: URL: https://github.com/apache/maven-war-plugin/issues/100#issuecomment-2967842350
**[Andreas Wuest](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kickmetondy)** commented Still having this problem. the following post will contain a patch, at least for the "ejb-client" type in the dependency. so here is what i found out. With the latest cvs snapshot it is not possible to add the ejb client to the war, always the ejb.jar will be added to the war file what is not really inteded. the project looks like : Parent - Project A (Ejb) - Project B (War) this dependency will only add the ejb(server).jar to the war file. What i really want is that the created ejb-client.jar is added to the war. adding the ejb(server).jar to the war file does not make sense for the war file. (the maven-ejb-plugin created a server and client version for the de.blubb.project_name.ejb projekt, which is actually another module of my project) \<dependency> \<groupId>de.blubb.project_name\</groupId> \<artifactId>ejb\</artifactId> \<version>1.0\</version> \<type>ejb-client\</type> \</dependency> If the patch is obsolete, i was wondering if there is anybody out there who is using the maven-ejb-plugin in combination with the maven-war-plugin and is actually adding the created ejb-client to the created war file successfully. As far as i can tell the maven-ejb-plugin creates a client (if requested) with the name \<artifcat>-\<version>-client.jar. however the maven-war-plugin does not respect the "-client" in the client's name. even if i set the "type" of the dependency to "ejb-client" it is still getting the "ejb.jar", not the "ejb-client.jar". My patch fixes this problem. i can provide a testcase that shows the current problem, if requested. sorry for the long comment. -- 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
