On 17/11/06, Jerome Louvel <[EMAIL PROTECTED]> wrote:
In Eclipse, when you auto-import classes, it propose you to pick the best one in a popup list, so it's very easy to resolve those conflicts.
Ditto with netbeans. That assumes that we should take the supposed restlet offer. One I've seen offered the mortbay jar file or restlet, just a bit closer to home.
However, I'm willing to consider renaming if we have name conflicts with core JDK classes (ie. in packages java.*). Does it sounds fair enough?
Yes, but I do understand the problem. Not nice, but a possibility might be to prefix? E.g. Container => RContainer (restlet container) instead of java.awt.Container. Another option to consider might be to map the chapter 5 names to restlet names in documentation, then use another name in Restlets? I suggest this on the basis that not everyone will be familiar with the dissertation names? My main concern is the user with a plain text editor for Java, when the list of imports grows to 12 or more. regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk
