What I was saying is that he can put it under a different artifact name. The only possible drawback with this approach is when a dependency depends of hibernate, it will include all the jars but anyway you don't know wich one is used so no problem there.
But if it's not a good practice then I suggest him to follow your advice. You are the expert after all. On 11/2/05, Yann Le Du <[EMAIL PROTECTED]> wrote: > > Even if it would indeed do the trick, IMHO I would not encourage it > because you > would have to copy-paste every time the POM is changed in Maven central > repository - and how would you be aware of such changes ? - or you want to > use > another Hibernate version. > > The "good practice" would be, as you suggested, to use the exclusions > feature - > not excludes - to specify the JARs you don't want. If you specified the > ones > you do want, then you wouldn't get new dependencies needed in subsequent > Hibernate versions. > > It works just fine for me. BTW, you can notice that Hibernate 3.0.5 POM > uses > this feature for dom4j :) > > Hope this helps, > Yann > > --- Robert Taylor <[EMAIL PROTECTED]> a écrit : > > > 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] > > > > > > > > > > > > > ___________________________________________________________________________ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada
