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 should not need all the internal dependencies of the server part.

However E is used in C, so we have

        <dependency>
                <groupId>...</groupId>
                <artifactId>E</artifactId>
                <type>ejb-client</type>
        </dependency>

in C's pom-file. As P1, P2 are used in E, we have similarly
        <dependency>
                <groupId>...</groupId>
                <artifactId>P1</artifactId>
                <type>jar</type>
        </dependency>

in E's pom-file.

The problem is that when building C with maven, all server-part
dependencies (P1, P2) are used (downloaded and put in the classpath)
also, which is unnecessary and unwanted.

Is there a way to specify the dependencies for E in a way that client
project only get what is really needed?

Any answers are appreciated! Thanks.


Reply via email to