| Re: [elk-dev] ELK Refactoring |
Yes, so far it seems to work well. Do we already have an update site? As soon as we have it we should include it in the Oomph setup, so when we add some kind of option / algorithm metadata language we can include that in our development IDE.
Miro
> On 10.01.2016, at 16:38, Christoph Daniel Schulze <cds@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi everyone,
>
> I have also changed the Oomph setup to include the new formatting options.
>
> Miro, did the Oomph setup work well for you? If so I'd consider asking
> Eike to include it in the official catalogue.
>
> Cheers,
> Christoph Daniel
>
> On 08/01/16 15:29, Christoph Daniel Schulze wrote:
>> Hi!
>>
>> On 23/12/15 15:50, Miro Spönemann wrote:
>>> — I would vote for changing the CheckStyle configuration to be less
>>> strict. In particular:
>>> - All header lines are marked with warnings. That check should be
>>> either corrected or removed.
>>> - Don’t insist on requiring any JavaDoc tags, especially @author. I
>>> would also vote for not requiring @param and @return since that leads to
>>> many stupid tags that don’t add any information, e.g. I found
>>> - Increase the maximal line length (e.g. to 120).
>>
>> I just fixed the header line issue and applied the two other changes.
>> Simply pull the new master and restart Eclipse (the Checkstyle plug-in
>> seems to load configuration files once on startup).
>>
>> Cheers,
>> Christoph Daniel
>
> _______________________________________________
> elk-dev mailing list
> elk-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/elk-dev
_______________________________________________
elk-dev mailing list
elk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/elk-dev