| We'll assume it is correct and Ivar can probably comment if that's not the case.
I've checked the file in so it can be under revision control.
I don't use Eclipse, however, so let me know if we really need it in zip format.
-- David Blevins 310-633-3852
In case the ruleset is considered an offical recommendation of the PMC, I want to kindly ask the PMC to publish the attached file in the EE4J WIKI. The ZIP contains the Eclipse formatting rules donated by Arjan Tijms. -Markus Well.. this means that WIKI page is NOT an official recommendation of the PMC…? Would be great if the PMC either removes that page or clearly gives it the status of an OFFICIAL recommendation, including all needed corrections or clarifications. -Markus Hi Markus, Ivar can probably comment on where that page came from. I suspect it's a carry over from Sun conventions in place when the code was donated. On that note I suspect we're already in wild-wild-west territory as I saw a javadoc fix from Arjan that completely reformatted all the code and pom.xml files. So I don't know what the convention actually is. In particular, the code was donated with xml files at 2 spaces and java files at 4 spaces. I'm not sure if the doc was intended to change it or was unspecific on the spacing for java vs other formats like xml or json. Ideally we do have a convention the majority likes and we actually stick to and is enforced with checkstyle plugin usage. Sharing files for IDE configuration would be a definite plus. There are recommendations for code style on https://github.com/eclipse-ee4j/ee4j/wiki/Code-Conventionsand I am pretty sure there are people having set up ready-to-use formatter rules configs for Netbeans and Eclipse IDEs. So I would be happy to find them uploaded into the WIKI to make it easier to contribute to EE4J subprojects. I'm writing this to the PMC because I assume that rules where decided by you and you already had such files at hand when deciding it. :-)
|
