On 8/31/2015 4:07 PM, Bryan Thompson wrote: ...
Apologies if I am behind the curve here. It would probably be easier for me to understand if the package namespace cleanup was proposed as a list of X => Y renames so I could look at the source tree and understand more clearly what is involved.
...
Good idea. It may be useful for the release notes, as well as for our discussion. I have started putting one together. Here is an arbitrary extract from the raw data: names_2.2.txt:./com/sun/jini/action/GetBooleanAction.java names_2.2.txt:./com/sun/jini/action/GetIntegerAction.java names_2.2.txt:./com/sun/jini/action/GetLongAction.java names_2.2.txt:./com/sun/jini/action/GetPropertyAction.java names_3.0.txt:./org/apache/river/action/GetBooleanAction.java names_3.0.txt:./org/apache/river/action/GetIntegerAction.java names_3.0.txt:./org/apache/river/action/GetLongAction.java names_3.0.txt:./org/apache/river/action/GetPropertyAction.java The "action" package keeps the same content. It changed from com.sun.jini.action to org.apache.river.action. That loses the strong internal-only use-at-your-own-risk implication that the com.sun packages had, so we need to do something else to mark these classes as not supported API. I will continue to work on building the package map. Patricia
