Rupert,

The exclusion shouldn't be needed anyway.   In the pom.xml for commons-lang, 
it's marked as <scope>test</scope>.  Thus, we wouldn't be pulling it in 
anyway.

Dan



On Monday 15 January 2007 07:52, Rupert Smith wrote:
> This seems to be due to the exclusion of junit (3.7.1) as an incorrect
> depency of commons-lang:
>
>    <dependency>
>        <groupId>commons-lang</groupId>
>        <artifactId>commons-lang</artifactId>
>        <version>2.1</version>
>
>        <exclusions>
>            <exclusion>
>                <groupId>junit</groupId>
>                <artifactId>junit</artifactId>
>            </exclusion>
>        </exclusions>
>    </dependency>
>
> Accoring to the article below, the exclusion from common-lang should not
> affect anything else. So the seperate declaration for junit 3.8.1 should
> not be wiped out by this. Removing the exclusion gets my build working
> though.
>
> http://maven.apache.org/guides/introduction/introduction-to-optional-and-ex
>cludes-dependencies.html
>
> Looks like a maven bug, can I suggest putting exclusions in the assembly
> descriptors instead?
>
> Still seems bizarre that this affected only me...
>
> On 1/15/07, Rupert Smith <[EMAIL PROTECTED]> wrote:
> > Well, I did a checkout going back to last thursday. It definitely built
> > for me then, but now I get the same error on that revision too. Must be
> > something with to do with maven, so I'll try a clean install of that and
> > see how I fare.
> >
> > On 1/15/07, Robert Godfrey <[EMAIL PROTECTED]> wrote:
> > > Works fine for me on a clean checkout...
> > >
> > > I have seen this before, but it was a problem with my local repository.
> > >
> > > Anyone else having problems?
> > >
> > > - Rob
> > >
> > > On 15/01/07, Rupert Smith < [EMAIL PROTECTED]> wrote:
> > > > Did a complete, clean checkout just now and even cleared my local
> > >
> > > maven
> > >
> > > > repository.
> > > >
> > > > I get an error compiling the unit tests, for example in the broker:
> > > > "package
> > > > junit.framework does not exist". This is quite strange, as I can see
> > >
> > > junit
> > >
> > > > set up in the parent pom under dependency management and declared as
> > > > a dependency in the broker pom.
> > > >
> > > > Is anyone else getting this error, or is it just me?

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]

Reply via email to