jira-importer commented on issue #52: URL: https://github.com/apache/maven-ejb-plugin/issues/52#issuecomment-2879259132
**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented Dennis has already outlined the reasons for which it is not possible to solve that within maven-ejb-plugin at the moment. May be we have to think about that. As suggest the simplest solution is having two ejb projects. Creating clientJarExclusions does not help cause the pom is the couting factor here. Otherwise the maven-ejb-plugin has to emit two supplemental pom files one for server and one for the client artifact. Some other thoughts i had during looking into the your examples: Why does the EJB has a dependency to a webservice (apart from that the EJB does not really contain code for a WebServices) ? It would make more sense have a webservice which has a dependency to the EJB (Model)... So an other path might be to define the dependencies of the webservices to the EAR module which means they would be packaged into the EAR file and so they are available on the path within the application server....which means you can remove those dependencies from the ejb package...which will solve the problem as well. BTW: Why defining an EJB 3.1 spec but defined only 3.0 version for EJB ? -- 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
