Let's consider a couple harsh realities:
We have extremely limited development resources, so ideas that require a lot of work just aren't practical right now
The reason to support both
org.eclipse binaries would be to spend extra effort right now to plan for a day that we might drop compatibility and migrate fully to
org.eclipse. But frankly, I don't see that day coming, and that's especially true if we never get a maintenance release out due to being bogged down by these issues
com.redhat, with the hope that this will be ok with RedHat and Eclipse
com.redhatname simply can't be used (even along side
org.eclipse), then the Eclipse Foundation will effectively be forcing the compatibility break and putting a stop to a maintenance release. The thing is, I have no idea if that is a concern of theirs or not.
ant test, and the like, as in the readme https://github.com/eclipse/ceylon-sdk
1.3.3compatible code - the
masterbranch is not compatible
_old/1.3.3-branchingshould probably work
ceylon testshould work.
ceylon.test. The rest are just standalone modules that happen to use the