Probably the best way to create patch to remove unused imports would be to use an IDE like Eclipse. It provides an easy way to "organise imports" for a project, which will:
- Sort the imports in the order you specify - Remove unused imports. You could then use Eclipse (or your favourite method) to generate a patch. Regards, Oliver > -----Original Message----- > From: Dominique Devienne [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 21 November 2002 07:23 > To: 'Jakarta General List' > Subject: RE: More fun with unused/duplicate/unnecessary import > statements > > > Being new to this particular list, may I inquire about the info gathering > and reporting tools used? Checkstyle? Others? Thanks. > > Any chance to be able to auto-generate bumbled patches per project fixing > the unused imports? > > Just asking ;-) --DD > > -----Original Message----- > From: Tom Copeland [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 2:17 PM > To: 'Jakarta General List' > Subject: More fun with unused/duplicate/unnecessary import statements > > Here's the same sort of report that I posted a couple weeks ago, but > this time it includes stuff like: > > ============ > package foo.bar; > import foo.bar.Baz; > public class Buz {} > ============ > > i.e., imports from the same package. Numbers are about the same.... > > http://cvs.apache.org/~tcopeland/bad_imports_20_nov_02.htm > > Yours, > > Tom > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
