[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-core-dev] Releasing formatter settings
|
Hi,
I do it as your advice, most thing is OK, besides of Enum class.
If save a Enum class, for example:
public enum Test {
ID,NAME;
}
got a error report, as follows:
The save participant 'org.eclipse.jdt.ui.postsavelistener.cleanup' caused an exception: java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: L/model/Test.java
eclipse.buildId=I20061102-1715
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux amd64-64 j9vmxa6423-20061001 (JIT enabled)
J9VM - 20060915_08260_LHdSMr
JIT - 20060908_1811_r8
GC - 20060906_AA
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=zh_CN
Command-line arguments: -os linux -ws gtk -arch x86_64 -clean
Regards,
Qinxian
2006/11/4, John Arthorne <John_Arthorne@xxxxxxxxxx
>:
As you may already know, 3.3 M3 now
has support for running things like code formatter and organize imports
on editor save. You can turn it on under Preferences > Java >
Editor > Save Participants. I recommend editing the default profile
and turning off format comments, since the core formatter conventions have
never formatted comments. Turning this on will make a big mess of
your code if you are not using the core formatter and organize import settings:
http://www.eclipse.org/eclipse/platform-core/documents/coding_conventions.html
To prevent this happening, I have released
the core formatter and organize import settings in the project preference
scope for all org.eclipse.core.* projects. Since we have manually
formatted all core projects according to these conventions in the past,
this will avoid mangling of your code when you commit changes.
Enjoy!
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev
--
向秦贤