I don't think we're looking at a full API rewrite. I think going to 1.5 can
help internally quite a bit. The new concurrent stuff may help sort out
issues we've had with thread safety, while at the same time allowing higher
levels of concurrency. From a project management perspective, we could
consolidate the various modules, which should lead to overall higher
productivity. And we could use generics internally without having to change
any public facing APIs.
In this case, targeting Java 5 may very well help get a Cayenne 3.0 release
out the door faster. And the resulting system could be of higher quality.
Personally, I think it'd be great if the public API supported generics as
well. This is admittedly a larger undertaking, but something
well-worthwhile in the long run. I'd be fine with deferring that, though,
until a subsequent release. In that case, I'd like to at least see the
generic velocity templates be provided as an out-of-the-box solution. These
clearly aren't the best solution, but may be an adequate stop-gap one.
-- KevinOn 8/13/07 7:43 PM, "Aristedes Maniatis" <ar..aniatis.org> wrote:
> > On 14/08/2007, at 4:11 AM, Kevin Menard wrote: > >> Since this is a bit of a big change for us, and Ari had expressed some >> concern, I'd like to just take a vote to ensure this is the >> direction we are >> heading. > > I certainly see the benefit in the longer term, but I wonder what the > purpose of this change is right now half way through the 3.0 > development process. Personally I'd like to see 3.0 out as soon as > possible, since it has been a long time since the last stable new > feature release (1.2) and I think releases help keep up the perceived > momentum of the project. > > Is the plan for 3.0 to not release until it has full JPA compliance? > If so, a release this year seems unlikely. > > Will moving to JDK 5 be a change in label only, or will we actually > go in and implement generics throughout all the classes, possibly > requiring some API changes along the way to do it right? Will this > then add 3-6 months to the release of 3.0 while the changes are > ironed out? Are there other JDK 5 features we desperately want to > use? I know that the Swing improvements could make the modeler nicer, > but that too requires a whole bunch of work. I've just done a lot of > work putting generics into my major project, and it isn't always as > simple as pressing the 'add generics to this class...' button in > Eclipse. > > * generics > * swing improvements > * nicer for loop (but very minor functional change or speed improvement) > * other little things > > So my hesitation is to do with feature creep. If moving to 1.5 adds > to the release schedule considerably, then I'm -1. > > > Sorry to sidetrack this vote with questions, but I'd like to be clear > about the benefits/costs of this decision. > > > Ari Maniatis > > > > > > --------------------------> > Aristedes Maniatis > phone +61 2 9660 9700 > PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 > >
--
This archive was generated by hypermail 2.0.0 : Mon Aug 13 2007 - 22:09:49 EDT