You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by Francesco Chicchiriccò <il...@apache.org> on 2013/08/02 12:19:56 UTC
Developing Olingo requires Eclipse?!?
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/
Re: Developing Olingo requires Eclipse?!?
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi,
I agree with your opinion.
I think it is currently just the case because the most of the developers
use eclipse.
But for the future we should switch to "maven" and tooling
(Checkstyle/PMD) which can be used with "maven".
Kind regards,
Michael
PS: I also use Netbeans if possible ;o)
On 02.08.13 12:19, "Francesco Chicchiriccò" <il...@apache.org> 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/
>
Re: Developing Olingo requires Eclipse?!?
Posted by "Klevenz, Stephan" <st...@sap.com>.
So, technically it seems to be working :-)
http://olingo.org/
The CMS structure is quite simple, there is only one template
(skeleton.html) and all the rest is just mdtext files. Feel free to add
and change content. Syntax highlighting is also welcome.
-- Stephan
On 02.08.13 12:45, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>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ò" <il...@apache.org> 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/
>
Re: Developing Olingo requires Eclipse?!?
Posted by Francesco Chicchiriccò <il...@apache.org>.
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ò" <il...@apache.org> 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/
Re: Developing Olingo requires Eclipse?!?
Posted by "Klevenz, Stephan" <st...@sap.com>.
Good point.
About the homepage: this is going completely to change: [1] 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.
--Stephan
[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ò" <il...@apache.org> 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/
>