Hi Dave, 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. Otherwise, it's just too hard to take into account all potential name conflicts, especially when names (inspired from REST and HTTP) are core to the problem domain you are addressing.
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? Does someone know a way to detect those potential name conflicts automatically? Piyush, can CheckStyle do that? Best regards, Jerome > -----Message d'origine----- > De : Dave Pawson [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 17 novembre 2006 12:37 > À : [email protected] > Objet : name conflicts > > I'm using netbeans which has a feature to resolve missing > import statements. > > Again and again I've found that restlet names are in conflict with > standard Sun names. > > This could cause quite a bit of confusion if done manually. > > regards > > -- > Dave Pawson > XSLT XSL-FO FAQ. > http://www.dpawson.co.uk
