Re: Coding standards?
For test coverage you can just run 'mvn cobertura:cobertura' which will give you coverage reports in target/site/cobertura/index.html. There might be other maven coverage plugins that do the same... Cheers, David On 24 September 2015 at 23:31, Sten Roger Sandvik <ste...@gmail.com> wrote: > Thanks Pierre! > > > > 2015-09-24 23:55 GMT+02:00 Pierre De Rop <pierre.de...@gmail.com>: >> Hi Sten Roger; >> >> For the coding standards, I think it's described in [1] (see the eclipse >> formatting template at the end of the page). >> >> With regard to test coverage, I'm not currently aware of any rules or >> reusable poms that could be used to run test coverages. >> >> >> [1] http://felix.apache.org/documentation/development/coding-standards.html >> >> cheers; >> /Pierre >> >> On Thu, Sep 24, 2015 at 11:01 PM, Sten Roger Sandvik <ste...@gmail.com> >> wrote: >> >>> Hi. >>> >>> Do we have any coding standards for Felix project? And, an unrelated >>> question, do we have some sort of test coverage reports? >>> >>> BR, >>> Sten Roger >>>
Re: Coding standards?
Thanks Pierre! 2015-09-24 23:55 GMT+02:00 Pierre De Rop <pierre.de...@gmail.com>: > Hi Sten Roger; > > For the coding standards, I think it's described in [1] (see the eclipse > formatting template at the end of the page). > > With regard to test coverage, I'm not currently aware of any rules or > reusable poms that could be used to run test coverages. > > > [1] http://felix.apache.org/documentation/development/coding-standards.html > > cheers; > /Pierre > > On Thu, Sep 24, 2015 at 11:01 PM, Sten Roger Sandvik <ste...@gmail.com> > wrote: > >> Hi. >> >> Do we have any coding standards for Felix project? And, an unrelated >> question, do we have some sort of test coverage reports? >> >> BR, >> Sten Roger >>
Coding standards?
Hi. Do we have any coding standards for Felix project? And, an unrelated question, do we have some sort of test coverage reports? BR, Sten Roger
Re: Coding standards?
Hi Sten Roger; For the coding standards, I think it's described in [1] (see the eclipse formatting template at the end of the page). With regard to test coverage, I'm not currently aware of any rules or reusable poms that could be used to run test coverages. [1] http://felix.apache.org/documentation/development/coding-standards.html cheers; /Pierre On Thu, Sep 24, 2015 at 11:01 PM, Sten Roger Sandvik <ste...@gmail.com> wrote: > Hi. > > Do we have any coding standards for Felix project? And, an unrelated > question, do we have some sort of test coverage reports? > > BR, > Sten Roger >
Re: Coding Standards [was [Quick vote] Coding Standard for Import Statements]
On 22/12/2007, Stefano Lenzi [EMAIL PROTECTED] wrote: Carsten Ziegeler wrote: I changed the subject for this general discussions, more comments below. Marcel Offermans wrote: If you don't mind, I do have a comment about this quick vote. Sure, I don't mind :) - quiet the opposite :) Let me start by stating that I think that coding standards are important. In fact, I was one of the people who pushed for them and came up with the draft for the first version of the document. However, I think the real discussion we should have is about formatting source code. Do we want to somehow make sure all code is formatted exactly the same? Does this mean we need to standardize on a single IDE or a separate formatting tool? I would like to propose the integration of maven-checkstyle-plugin in order main POM so that we can keep an eye on non-complaint sources. Furthermore, we can store the checkstyle and formatter configuration in our SVN repository, as many projects do. we use checkstyle over at OPS4J and have our Eclipse formatter config in svn, and it's worked out well - using checkstyle is a great way to monitor the code Also by exploiting a common public location (the SVN repository in this case) containing a set of configuration file (both for checksyle and code formatting) we can auto-configure IDEs by an ad-hoc tuned POM. What do you think? +1 (non-binding) I'd find this very useful -- Cheers, Stuart
Re: Coding Standards [was [Quick vote] Coding Standard for Import Statements]
Carsten Ziegeler wrote: I changed the subject for this general discussions, more comments below. Marcel Offermans wrote: If you don't mind, I do have a comment about this quick vote. Sure, I don't mind :) - quiet the opposite :) Let me start by stating that I think that coding standards are important. In fact, I was one of the people who pushed for them and came up with the draft for the first version of the document. However, I think the real discussion we should have is about formatting source code. Do we want to somehow make sure all code is formatted exactly the same? Does this mean we need to standardize on a single IDE or a separate formatting tool? I would like to propose the integration of maven-checkstyle-plugin in order main POM so that we can keep an eye on non-complaint sources. Furthermore, we can store the checkstyle and formatter configuration in our SVN repository, as many projects do. Also by exploiting a common public location (the SVN repository in this case) containing a set of configuration file (both for checksyle and code formatting) we can auto-configure IDEs by an ad-hoc tuned POM. What do you think?
