Skip to main content

[VOTE] Remove old databinding

12 replies [Last post]
rbair
Offline
Joined: 2003-07-08

Simple vote: remove old org.jdesktop.binding packages?

Justification: Maintaining the old binding API will take energy and time we don't have. Folks ought to migrate to the new binding API -- or wait and see what Scott develops on another branch -- or wait and see what happens with JSR 227. In any case, using the old binding API is a Bad Thing.

+1 from me

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
2starr
Offline
Joined: 2004-03-29

+1

rbair
Offline
Joined: 2003-07-08

Wow, ok this is a really old thread. Anyway, the vote passes. I've tagged the files (removed_old_binding) and will now remove the old binding.

Richard

Kleopatra

jdnc-interest@javadesktop.org wrote:
> Wow, ok this is a really old thread. Anyway, the vote passes. I've tagged the files (removed_old_binding) and will now remove the old binding.
>

you forgot to tag the dependent projects as well. Obviously, demos, jdnc
and most incubator builds are failing now (doesn't show in CC because it
withdraw with a hick-up).

We don't have any procedural rules (doesn't matter so much, if we had we
would break them anyway ;-) about such drastic changes but in the past
we used to post a prominent thread to prepare developers for the storm
waves to be expected.

Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Richard Bair

>you forgot to tag the dependent projects as well. Obviously, demos, jdnc
>and most incubator builds are failing now (doesn't show in CC because it
>withdraw with a hick-up).

doh. I now about the demos problem -- working on that. Incubator is, of
course, a bigger problem. The proper thing to do is to do a build containing
the old binding and put that jar in the incubator.

>We don't have any procedural rules (doesn't matter so much, if we had we
>would break them anyway ;-) about such drastic changes but in the past we
>used to post a prominent thread to prepare developers for the storm waves
>to be expected.

I thought the VOTE thread was just such a prominent thread.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Patrick Wright

On 1/13/06, jdnc-interest@javadesktop.org wrote:
> Simple vote: remove old org.jdesktop.binding packages?
>
> Justification: Maintaining the old binding API will take energy and time we don't have. Folks ought to migrate to the new binding API -- or wait and see what Scott develops on another branch -- or wait and see what happens with JSR 227. In any case, using the old binding API is a Bad Thing.
>
> +1 from me

+1 from me, but I would say we create an archive--or maybe make sure
we keep the 0.8 release around (source and build) for people who
either are using it (like Neil) or want to look at it.

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dhall
Offline
Joined: 2006-02-17

+1

Tagging with a branch tag should be good enough: Neil or anyone else in his situation can still get to the source.

We should keep old release packages around, but unless we change respositories, we can always recreate

Dave

Noel Grandin

In that case please tag/branch the existing state of the binding repository,

I have a production app that uses it, and I still have patches not yet
incorporated into binding (specifically, issue #25)

Thanks,
Noel Grandin

jdnc-interest@javadesktop.org wrote:

>Simple vote: remove old org.jdesktop.binding packages?
>
>Justification: Maintaining the old binding API will take energy and time we don't have. Folks ought to migrate to the new binding API -- or wait and see what Scott develops on another branch -- or wait and see what happens with JSR 227. In any case, using the old binding API is a Bad Thing.
>
>+1 from me
>---
>[Message sent by forum member 'rbair' (Richard Bair)]
>
>http://www.javadesktop.org/forums/thread.jspa?messageID=136645
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
>For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>
>
>
>

NOTICE: Please note that this email, and the contents thereof,
are subject to the standard Peralex email disclaimer, which may
be found at: http://www.peralex.com/disclaimer.html

If you cannot access the disclaimer through the URL attached
and you wish to receive a copy thereof please send
an email to email@peralex.com

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08

> In that case please tag/branch the existing state of
> the binding repository,

Will do. There are 2 more days of voting, so Monday if the vote passes I'll do so.

Amy Fowler

On Jan 12, 2006, at 4:52 PM, jdnc-interest@javadesktop.org wrote:
>
> Justification: Maintaining the old binding API will take energy and
> time we don't have. Folks ought to migrate to the new binding API
> -- or wait and see what Scott develops on another branch -- or wait
> and see what happens with JSR 227. In any case, using the old
> binding API is a Bad Thing.

I wouldn't characterize it as "Bad", but more "out of style" :-)
just had to throw that in as the one who originally created that API
2 years ago....

Aim

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Richard Bair

Hey Amy,

>>Justification: Maintaining the old binding API will take energy and time
>>we don't have. Folks ought to migrate to the new binding API -- or wait
>>and see what Scott develops on another branch -- or wait and see what
>>happens with JSR 227. In any case, using the old binding API is a Bad
>>Thing.
>
>I wouldn't characterize it as "Bad", but more "out of style" :-)
>just had to throw that in as the one who originally created that API 2
>years ago....

Argh! No, I don't mean to say the old binding API is a Bad Thing, but that
maintaining multiple APIs is! The new "in style" API is mearly your API
fleshed out (still has DataModel, Binding, Conversion, etc)! Sorry if that
came off wrong :(

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rturnbull
Offline
Joined: 2005-08-27

> Simple vote: remove old org.jdesktop.binding
> packages?
>

+1 from me

Are you going to replace them with the new binding at this time.
If so this is more than just removing org.jdesktop.binding packages.
Its replacing nearly the whole binding project.

rbair
Offline
Joined: 2003-07-08

> Are you going to replace them with the new binding at
> this time.
> If so this is more than just removing
> org.jdesktop.binding packages.
> Its replacing nearly the whole binding project.

That's a second vote we'll start next week. The new binding will definitely be available, in pre-built format on the downloads page. The only question is whether it is ready to be moved into the trunk. Lets talk about this more next week (don't want to side track this thread).

Richard