Guys, I don't care what happens where--we can use
trunk for generics work, but I would like the option
of finishing a non-generic version of the lib (branch
is fine by me) so we can evaluate the difficulty of
swapping it out for the similar parts of a (also
non-generic) Collections 4.0.
-Matt
--- James Carman <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 1, 2008 at 1:06 PM, sebb
> <[EMAIL PROTECTED]> wrote:
> >
> > I'd suggest leaving them with the Java files,
> assuming that they are
> > related to each other.
> > [JMeter has some beans with related property
> files; these are easy to
> > maintain because the files are all in the same
> directory. It would be
> > a bit of a pain otherwise.]
> >
> > src/main/resources seems more suitable for common
> resources shared by
> > lots of files.
> >
> > BTW, +1 to reviving the project.
> >
>
> Since there are so many folks interested in reviving
> it, do you guys
> want to split up the work of "genericizing" the
> classes? We could
> split it up by packages?
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total
Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
