Noel, Like Sandro, I would prefer to see a less intrusive change if possible, but I am not familiar with the package.
Would this help? - rename org.apache.pivot.wtk.text.Span to org.apache.pivot.wtk.text.TextSpan - recreate org.apache.pivot.wtk.text.Span as a deprecated subclass of org.apache.pivot.wtk.text.TextSpan (with some javadoc notes explaining its purpose) Then you could use org.apache.pivot.wtk.Span and together org.apache.pivot.wtk.text.TextSpan without qualifying them, and there shouldn't be a clash with (the newly created & deprecated) org.apache.pivot.wtk.text.Span. Any other code using org.apache.pivot.wtk.text.Span would be flagged as containing a deprecated class (assuming the warnings are not ignored), so the transition between Span & TextSpan could happen at the leisure of the end user. I see there is also a org.apache.pivot.wtk.text.List class. Do the same hassles exist with that, or no so much as the API and intent are so different between it and org.apache.pivot.collections.List? Chris On 4 August 2011 13:53, Sandro Martini <[email protected]> wrote: > Hi Noel, > Of course in a maintenance release an incompatible change like this is not > the best, but for me no problem, go with the change. Maybe only report this > change in a jira ticket, so will be visible in release notes. > > Bye > Il giorno 04/ago/2011 08:44, "Noel Grandin" <[email protected]> ha > scritto: >> Hi >> >> I'd like to rename Span to TextSpan because I keep having to specify the > fully qualified class name in code where we are >> using both >> wtk.text.Span >> and >> wtk.Span >> >> Any objections? >> >> -- Noel >
