Hi Greg, [EMAIL PROTECTED] wrote on Wednesday, September 20, 2006 5:53 PM:
> "Jörg Schaible" <[EMAIL PROTECTED]> wrote on > 09/20/2006 10:34:26 AM: > >> Hi Greg, >> >> [EMAIL PROTECTED] wrote on Wednesday, September > 20, 2006 4:45 > PM: >> >>> "Jörg Schaible" <[EMAIL PROTECTED]> wrote on >>> 09/20/2006 03:24:46 AM: >>> >>>> (*) New release of JMock 1.1.0 still uses cglib:cglib-full:2.0 as >>>> dependency although this breaks any app using Hibernate 3.x or >>>> Groovy. Better would have been to use cglib:cglib-nodeps:2.1_3, but >>>> as the official docs state the bad dependency, it is also >>>> referenced in the POM on ibiblio. Is this Carlos' fault now? >>> >>> I renamed the thread because this is tangent to it. I've also hit >>> this error. How did you work around it? I was brand new to maven >>> when we hit it and I did the following, but I'm not certain it is >>> the best solution. >>> >>> <dependency> >>> <groupId>jmock</groupId> >>> <artifactId>jmock</artifactId> >> >> You mean "jmock-cglib" ... plain jmock does not have that dep :) > > Strange. I actually copied and pasted out of my pom. I didn't exclude > from jmock-cglib: > <dependency> > <groupId>jmock</groupId> > <artifactId>jmock-cglib</artifactId> > <version>1.0.1</version> > <scope>test</scope> > </dependency> > > I wonder if this is a jmock 1.0.1 vs. 1.1.0 difference. I'll > double check > the dependency tree in the -X output, but what I pasted is what we're > using. I guess I'll also see what's new in jmock 1.1.0. No, but exclusions work currently globally (MNG-1797) ;-) >>> <version>1.0.1</version> >>> <scope>test</scope> >>> <exclusions> >>> <exclusion> >>> <artifactId>cglib-full</artifactId> >>> <groupId>cglib</groupId> >>> </exclusion> >>> </exclusions> >>> </dependency> >> >> Yes, this is what we do, but in the dependencyManagement section of >> our "global" POM. > > Nice idea. I was just reading about what those > dependencyManagement and > pluginManagement sections are for the other day, but I didn't see a > concrete application of them. Thanks for the tip. We do have > a "basepom" > shared by a few teams. But be careful with those exclusoins ... since they work global from the first time the artifact is considered that has the exclusion. Since the artifacts are kept in a hash map and the algorithm runs over the keyset, this sequence might change with every added dep :-/ - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
