On Friday 25 April 2008 Arand, Thomas (NSN - DE/Muenich) wrote: >> Is that really the only way to deal with that? >> 1. has the disadvantage that some other project indeed may need the >> server dependencies (e.g. the artifact to package an ear). With this >> solution one would have to repeat the dependency in that other project, >> what is definitely not wanted.
>While I agree with you that the 2 provided solutions are more workarounds >than solutions, I have to say that if a project needs some server >dependencies, it has to declare it anyway and should not rely on transitiv >dependencies. In principle you are right, but not in this particular case. When building the ear file for an EJB (note that this is done in another maven project than the EJB project itself) one step is the calculation of the classpath that must be set to run the server-part of the EJB. For this step the affected maven-plugin uses the transitive dependencies of the EJB project. - Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
