Is this the only API change in the patch?
If so, I'm OK with doing this particular kind of change in a maintenance
release. Yes, it's technically an API change, but it shouldn't break
any existing code, and the change should enables clients to work with DTP
in a little less hacky way.
DTP PMC Lead
Data Tools Development
IBM Silicon Valley Laboratory
Brian Fitzpatrick <bfitzpat@xxxxxxxxxx>
DTP PMC mailing list
07/27/2011 12:54 PM
regarding API changes in a maintenance release and BZ342411
The bug reporter was kind enough to create a patch, but the patch involves
changing a the visibility of a private member variable and method to protected
in an API-level class (org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCTable).
What is our policy as far as API-level changes go in maintenance releases?
I'd like to get this fix into 1.9.1 because it may in fact help with some
of the other MySQL issues that have been reported. But - I'm leery of making
an API change for 1.9.1.
Any input would be great.
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat