Re: JUnit 4.4 released

Mauro,

The idea was to bundle only hamcrest-core, a small package that the
hamcrest team has told us is likely to change very rarely.  The
majority of the hamcrest matchers are in hamcrest-library, which can
be downloaded separately.  So, to get all of JUnit and all of
Hamcrest, without overlaps, you would download junit-x.x.jar, and
hamcrest-library-x.x.jar.

There are downsides to this arrangement.  My initial guess is that the
number of people who will find themselves with classpath problems
because they're using an incompatible version of hamcrest-all will be
less than the number who would have found themselves with classpath
problems because they don't have hamcrest, or couldn't figure out
which junit jar to download.

Of course, experience has a way of proving me wrong.  We'll see.

   David Saff

On 7/29/07, Mauro Talevi <[email protected]> wrote:
> David,
>
> David Saff wrote:
>
> > - To allow compatibility with a wide variety of possible matchers,
> >   we have decided to include the classes from hamcrest-core,
> >   from the [Hamcrest][] project.  This is the first time that
> >   third-party classes have been included in JUnit.
> >
> > [Hamcrest]: http://code.google.com/p/hamcrest/
> >
>
> Bundling classes from a dependent library in the jar will lead to classloader hell unless you
> change package name for the bundled classes.  jMock has Hamcrest as a mandatory but separate
> dependency.   Any reason you did not consider to do the same?  The compatibility motivation you cite
>   is not clear.  It is exactly for compatibility reasons that jars should be kept separate.  If a
> user wants to upgrade to a different version of hamcrest, it will conflict with the classes bundled.
>
> Alternatively, you could provide a *separate* jar (eg junit-all.jar) which bundles with the
> dependencies, but keeping junit.jar without dependendencies bundled.
>
> Thanks and regards,
> Mauro
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Junit-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/junit-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/