Alexandre,
Thanks for the prompt response!
I'll give your suggestion a try.
/robert
Alexandre Poitras wrote:
Oh and don't forget to change your dependencies in your pom to point on your
new Hibernate version. Hope this help!
On 11/2/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
In my opinion, what you can do is define somewhere in your internal
repository, a "light" version of hibernate. You just copy the hibernate jar
and pom in another location and then you remove the dependances you don't
want in the pom. This way, you keep the regular version of hibernate but you
can use your light version for any number of projects.
On 11/2/05, Robert Taylor <[EMAIL PROTECTED] > wrote:
Greetings, I'm new to Maven and am using Maven 2.0.
I'm trying to build a web application. That application has some
dependencies such as Hibernate3 and Spring. The transitive dependency
feature of Maven is copying in several .jar files which I don't
necessarily need at run time because I'm not using those particular
features of Hibernate3 and Spring. Is there a way to only have Maven
copy over those dependencies that are explicitely defined or do I have
to use the "excludes" feature to exclude those dependent dependencies
which I don't need.
/robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandre Poitras
Québec, Canada
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
