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
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
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.
2. would
Hi Thomas!
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
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.
Transitive deps are great, but if your current project requires some
artifacts itself, then it should/must declare them itself.
Otherwise,
Hi all,
we have the following problem with our ejb project (say E). This project
has many dependencies to other projects (e.g. P1, P2, ...), but these
are only used for the server-part of the ejb. That means especially, if
a client project (say C) use our ejb, they only need the client part.
They
Two options off the top of my head...
1. Set the P1, P2 dependencies to be optional in E.
2. Specify explicit excludes in C for P1, P2.
Wayne
On 4/23/08, Arand, Thomas (NSN - DE/Muenich) [EMAIL PROTECTED] wrote:
Hi all,
we have the following problem with our ejb project (say E). This project
