Adding named params won't break things (actually I was thinking of adding this to a 1.x release as well), but removing deprecated code will. Also, I was thinking of switching to only supporting named params in the 2.x branch.
I guess the real question is, do folks think that forcing the use of named params and switching to a groupid to org.apache is enough benefit for the cost? My vote, yes... keep a 1.x branch around for those who cannot or won't change, and 2.x for those who can. Bill- On Dec 13, 2012 8:04 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote: > We only need to change the coordinates if the package name changes to > account for BC breakage. > > Gary > > On Dec 13, 2012, at 17:47, William Speirs <wspe...@apache.org> wrote: > > > I just submitted > > DBUTILS-105<https://issues.apache.org/jira/browse/DBUTILS-105> to > > add support for named params to DB Utils. I'm thinking that if we wrapped > > that up with DBUTILS-95 < > https://issues.apache.org/jira/browse/DBUTILS-95> > > and DBUTILS-92 <https://issues.apache.org/jira/browse/DBUTILS-92> it > would > > be worth cutting a new major version. > > > > Also, we should switch the maven convention which probably means changing > > to commons-dbutils2 much like was done with lang. > > > > Thoughts? > > > > Bill- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
