On 17-May-04, at 09:58 Uhr, [EMAIL PROTECTED] wrote:
I built jelly from CVS and replaced the one maven uses with the generated
jar, and there's only one failing test case.
Which one ?
I seem to be reaching problem free building with my corrected dependencies and maven current cvs snapshot.
This was without replacing dom4j.Maybe was the difference.
If we can fix that one test case, we can look at the differences between the new jar and Maven's and work out what the benefit is to moving to the new one and dom4j 1.5.
How does that sound?
Sure... I hope I'll be able to commit my little changes which make me build fine. Mostly dependency management.
I'd also like to push for a beta release of Jelly soon.
I think everyone would like to have this but... do people have enough time?
Unless we can split/distribute responsabilities, I don't think I can do it.
A good thing would be, for example, to restrict the release on a (very) limited set of projects and sub-projects. I would be willing to babysit the swing, xml, log, util and beanshell tag-libs, maybe a bit more (e.g. ant, bsf, fmt, http), also maybe the core.
Could Jelly interested speak more about their interests.
I think we should release those things that we know the usages of and I wouldn't be entirely bothered to drop a few things out of the release... at least at first shot.
paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
