Andreas,
I think you are missing my point. If you declare this:
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>4.7</version>
<classifier>jdk15</classifier>
<exclusions>
<exclusion>
<groupId>bsh</groupId>
<artifactId>bsh</artifactId>
</exclusion>
</exclusion>
</dependency>
This will be as if testng did not declare it and yours will be used
instead. It may be a good idea to make it optional in the testng pom
if it really is optional, as well.
I'd certainly be in favour of having testng split this functionality
into a separate JAR to make it simpler, but its not a requirement.
Maybe Jesse K has an opinion?
- Brett
On 4/19/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
> Brett,
>
> Beanshell classes are included in both TestNG jar files (1.4 and 1.5).
> Probably to make the inclusion on the classpath easier. There are also
> other dependencies included.
>
> It might be better to have different flavors of jar files for TestNG. I
> often see projects that have a all-dependency jar file in addition to
> "pure" onces we the developer has to include all dependencies and that
> might be a good suggestion for testng as well.
>
> I am going to write an email to the testng user mailing list.
>
> Andreas
>
>
> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 17, 2006 5:18 PM
> To: Maven Users List
> Subject: Re: [M2] Force order of jar files in classpath
>
> On 4/18/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
> > Maybe it is indeed in this particular case a problem with the eclipse
> > plug-in and the request should go against the eclipse plug-in to honor
> > the order of dependencies within the pom.xml.
>
> I don't think either are deliberately maintaining the order of the
> pom, and because of transitive dependencies that would be fragile.
> Really what you want is to exclude test NG and its dependencies from
> your eclipse classpath because the eclipse testng plugin already takes
> care of it, right?
>
> Regardless, I'm not sure why the bsh from testng is added to the
> eclipse classpath. That could be a bug, or it could be that it is
> selected in preference to your own and just not seen during testing in
> Maven. Either way, the exclusions in your pom would solve the problem
> in eclipse.
>
> >
> > Regarding jaxb: I am using the xjc with a modified
> jaxb2-maven-plugin.
> > I have removed in the modified plug-in all Java 5 usage in order to
> get
> > it to run with Jaxb1.
> >
> > Is there another jaxb1 plug-in available that might do the job for me?
> >
>
> Someone has recently proposed contributing it to mojo.codehaus.org.
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
