Community
Participate
Working Groups
Build Identifier: M20100909-0800 @formatter:off tag does not work, even though it's enabled. Formatting the class results in the array being formated to 1 line (as set in my formatter profile). Setting this tag to off in the beginning of the class also does not work. I'm using Eclipse for Java Developers. Reproducible: Always Steps to Reproduce: 1.1) an example array: private static Object[] name = { Object1; Object2; etc... }; 1.2) apply formatter tags: //@formatter:off private static Object[] name = { Object1; Object2; etc... }; //@formatter:on Result: array is formated. 2) put the tag in the beginning of the class: /** * @author yournamehere * @formatter:off */ Result: all class is still formatted.
I couldn't reproduce using the default profile (Eclipse built in) + formatter on/off tags enabled (build I20101214-0800). Both, array case and putting the off tag before the class declaration, work fine for me. Can you please attach your formatter settings here? (You may also want to check with the latest I build or 3.7M4 build). Thanks.
Created attachment 185547 [details] Java Code Style preferences
(In reply to comment #2) > Created an attachment (id=185547) [details] [diff] > Java Code Style preferences Umm..I was specifically looking for the formatter settings in a .xml format. To get them, you can go to Java>Code Style>Formatter, make sure your formatter profile is showing, click edit and then click 'Export.." (on the top right). Please attach the xml file you get here. Thanks!
Created attachment 185566 [details] formatter
(In reply to comment #4) > Created an attachment (id=185566) [details] [diff] > guess 3 times Thanks! Unfortunately, I still couldn't reproduce, even with your formatter settings. Can you please try the latest build?
I'll download SR1 and M4 now.
Created attachment 185589 [details] before formatting, SR1
Created attachment 185590 [details] after formatting, SR1
With default formatter, just plain extracted and ran the Eclipse and opened a known class, didn't change absolutely anything. I'll try with Indigo M4 now.
Okay, those 2 screens can be discarded, forgot to enable that tag in SR1. Works fine in SR1 and M4, but not in my current setup.
(In reply to comment #10) > Okay, those 2 screens can be discarded, forgot to enable that tag in SR1. Works > fine in SR1 and M4, but not in my current setup. Will you be able to share your setup so that we can debug and find out the problem? Maybe something got messed up in your workspace and caused the problem. There's nothing much we can do unless we can reproduce the issue.
It'll be great if you can just use M4 instead since it works fine for you!
(In reply to comment #12) > It'll be great if you can just use M4 instead since it works fine for you! I'm thinking of doing just that, current one suddenly refused to recognise one of my projects... But AFAIK M4 is a developer (unstable) build, shouldn't there be some problems?
(In reply to comment #13) >[..] > But AFAIK M4 is a developer (unstable) build, shouldn't there be some problems? M4 is a milestone build and we do everything on our side to make sure it is stable. So you can surely go ahead and use it. Anyway, if you do have some doubts, you can surely use 3.6.1 or the soon to be released 3.6.2 until 3.7 comes out. Thanks! Closing as WORKSFORME
K then, hopefully there will be no problems :)
(In reply to comment #11) > Will you be able to share your setup so that we can debug and find out the > problem? Maybe something got messed up in your workspace and caused the > problem. There's nothing much we can do unless we can reproduce the issue. You mean all the preferences?
(In reply to comment #16) > [..] > You mean all the preferences? I meant your workspace, including source code, could help us find what went wrong in your workspace. But i'm sure its not a bug since its otherwise not reproducible, so let's just stick to the good builds for now. :)
(In reply to comment #17) > (In reply to comment #16) > > [..] > > You mean all the preferences? > > I meant your workspace, including source code, could help us find what went > wrong in your workspace. But i'm sure its not a bug since its otherwise not > reproducible, so let's just stick to the good builds for now. :) Yeah, can't do that. >40k files, good part of it is stuff I wouldn't want to show anyone. Hopefully this is the last time I'm here.
Verified for 3.7 M5 using build id: I20110124-1800
