On Wednesday 01 December 2010 6:01:14 am Dennis Sosnoski wrote:
Tried this, even going with the default workspace this time, rather than
the one I'd specified before. Still the same results, though.
I did have two Checkstyle sheets in the project properties, so I went
into my Eclipse
Should be all fixed now. I had to rely on a snapshot of buildtools as I
needed to update the checkstyle rules a bit, but I'll release that with 2.3.1
hopefully later today if I'm nothing else major pops up and I can somehow get
out of meeting hell.
Dan
On Wednesday 01 December 2010
I'm running on Linux (OpenSUSE 11.3, 32bit). Eclipse shows the file
encoding as UTF-8 (inherited from container).
I've checked the hexdump of some of the files and confirmed there is no
0x character present. I did notice that the //CHECKSTYLE:ON line
in these files was right at the end, and
On Friday 26 November 2010 6:47:11 pm Dennis Sosnoski wrote:
My original message is included in this one, at the bottom. There are
three different variations of Checkstyle errors: 1) unexpected char:
0x; 2) Missing a header - not enough lines in file; and 3) Wrong
order for import.
I've followed the instructions at
http://cxf.apache.org/setting-up-eclipse.html to create an Eclipse
project using the current trunk code, but Eclipse gives me a bunch of
Checkstyle errors as well as a bunch of warnings. Here's a
representative sampling of the Checkstyle errors (89 in all):
Got
Had the subversion plugin, but was missing subversion itself on the
system I was using. :-) Installed that, installed the matching version
of subclipse, deleted and re-imported the projects, and now I'm left
with just the errors.
Thanks,
- Dennis
On 11/27/2010 02:53 AM, Benson Margulies
My original message is included in this one, at the bottom. There are
three different variations of Checkstyle errors: 1) unexpected char:
0x; 2) Missing a header - not enough lines in file; and 3) Wrong
order for import.
- Dennis
On 11/27/2010 11:04 AM, Benson Margulies wrote:
Sigh. I
WHat platform are you on? have you set file.encoding to something interesting?
On Fri, Nov 26, 2010 at 6:47 PM, Dennis Sosnoski d...@sosnoski.com wrote:
My original message is included in this one, at the bottom. There are
three different variations of Checkstyle errors: 1) unexpected char: