On 02/08/2013 12:38, Klevenz, Stephan wrote:
Good point.
About the homepage: this is going completely to change: [1]
I really like [1], good job :-)
For the sake of perfection, do you think it is possible to add some
syntax highlight to code blocks?
Currently I am
pimping it by [2] and I like the documentation page of [3]. Here we can
add a section for development environment support like Eclipse and also
Netbeans. All of this is currently work in progress.
About the coding conventions I agree that checkstyle should lead and we
should have some written ruleset. Templates are then just for convenience
and can be provided for each kind of IDE.
+1
Regards.
[1] http://olingo.staging.apache.org
[2] http://html5boilerplate.com/
[3] http://isis.apache.org/documentation.html
On 02.08.13 12:19, "Francesco Chicchiriccò" <[email protected]> wrote:
Hi all,
do you think that the strong dependency on Eclipse claimed on the
project's homepage could be relaxed a bit? The text says:
The project build with Maven. To consume sources execute
mvn eclipse:clean eclipse:eclipse
and import generated projects into Eclipse. The project has a strict
coding convention and Eclipse templates are available here: Eclipse
Code Convention Templates. Best practice is to import these templates
to Eclipse workspace and do a "Code CleanUp" before each commit.
For example, since I am on Netbeans I don't need any preliminary command
in order to work with Olingo sources and Maven.
About code convention, would it be possible do refer to some general
rules that can be enforced via Checkstyle (for example)?
WDYT?
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
