You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Oliver B. Fischer" <o....@swe-blog.net> on 2014/11/29 14:50:14 UTC
Tools for code analysis
Dear all, before touching the whole build I would like to hear your opinion on the integration of tool support for code analysis in our build chain.
I would like to integrate the following tools in our build chain:
- Findbugs
- Checkstyle
- jQassistant
jQassistant is a quite new tool. It allows to import a code basis ( also Maven POMs) into Neo4j and to validate custom constraints expressed as graph query.
To ensure a fast build they must be triggered by a setting a property or a Maven profile. Later we can decide to have hard constraints which must be fullfilled for a release.
Wdyt?
Best,
Oliver
Von meinem iPhone gesendet
Re: Tools for code analysis
Posted by Otávio Gonçalves de Santana <ot...@gmail.com>.
I like the sonar
On Sat, Nov 29, 2014 at 12:10 PM, John D. Ament <jo...@gmail.com>
wrote:
> Apache provides a sonar instance:
> https://wiki.apache.org/general/SonarInstance
>
> We also have to add RAT checks to the build.
>
> On Sat, Nov 29, 2014 at 9:07 AM, Andres Almiray <aa...@gmail.com>
> wrote:
>
> > I'll add JaCoCo for code coverage, and Sonar if we have access to a Sonar
> > server @ apache.
> >
> > We can also use coveralls.io to keep track of coverage changes across
> > time.
> >
> > Cheers
> > Andres
> >
> > Sent from my primitive Tricorder
> >
> > > On 29/11/2014, at 14:50, Oliver B. Fischer <o....@swe-blog.net>
> > wrote:
> > >
> > > Dear all, before touching the whole build I would like to hear your
> > opinion on the integration of tool support for code analysis in our build
> > chain.
> > >
> > > I would like to integrate the following tools in our build chain:
> > >
> > > - Findbugs
> > > - Checkstyle
> > > - jQassistant
> > >
> > > jQassistant is a quite new tool. It allows to import a code basis (
> also
> > Maven POMs) into Neo4j and to validate custom constraints expressed as
> > graph query.
> > >
> > > To ensure a fast build they must be triggered by a setting a property
> or
> > a Maven profile. Later we can decide to have hard constraints which must
> be
> > fullfilled for a release.
> > >
> > > Wdyt?
> > >
> > > Best,
> > > Oliver
> > >
> > > Von meinem iPhone gesendet
> >
>
--
Otávio Gonçalves de Santana
blog: http://otaviosantana.blogspot.com.br/
twitter: http://twitter.com/otaviojava
site: *http://about.me/otaviojava <http://about.me/otaviojava>*
55 (11) 98255-3513
Re: Tools for code analysis
Posted by "John D. Ament" <jo...@gmail.com>.
Apache provides a sonar instance:
https://wiki.apache.org/general/SonarInstance
We also have to add RAT checks to the build.
On Sat, Nov 29, 2014 at 9:07 AM, Andres Almiray <aa...@gmail.com> wrote:
> I'll add JaCoCo for code coverage, and Sonar if we have access to a Sonar
> server @ apache.
>
> We can also use coveralls.io to keep track of coverage changes across
> time.
>
> Cheers
> Andres
>
> Sent from my primitive Tricorder
>
> > On 29/11/2014, at 14:50, Oliver B. Fischer <o....@swe-blog.net>
> wrote:
> >
> > Dear all, before touching the whole build I would like to hear your
> opinion on the integration of tool support for code analysis in our build
> chain.
> >
> > I would like to integrate the following tools in our build chain:
> >
> > - Findbugs
> > - Checkstyle
> > - jQassistant
> >
> > jQassistant is a quite new tool. It allows to import a code basis ( also
> Maven POMs) into Neo4j and to validate custom constraints expressed as
> graph query.
> >
> > To ensure a fast build they must be triggered by a setting a property or
> a Maven profile. Later we can decide to have hard constraints which must be
> fullfilled for a release.
> >
> > Wdyt?
> >
> > Best,
> > Oliver
> >
> > Von meinem iPhone gesendet
>
Re: Tools for code analysis
Posted by Andres Almiray <aa...@gmail.com>.
I'll add JaCoCo for code coverage, and Sonar if we have access to a Sonar server @ apache.
We can also use coveralls.io to keep track of coverage changes across time.
Cheers
Andres
Sent from my primitive Tricorder
> On 29/11/2014, at 14:50, Oliver B. Fischer <o....@swe-blog.net> wrote:
>
> Dear all, before touching the whole build I would like to hear your opinion on the integration of tool support for code analysis in our build chain.
>
> I would like to integrate the following tools in our build chain:
>
> - Findbugs
> - Checkstyle
> - jQassistant
>
> jQassistant is a quite new tool. It allows to import a code basis ( also Maven POMs) into Neo4j and to validate custom constraints expressed as graph query.
>
> To ensure a fast build they must be triggered by a setting a property or a Maven profile. Later we can decide to have hard constraints which must be fullfilled for a release.
>
> Wdyt?
>
> Best,
> Oliver
>
> Von meinem iPhone gesendet
Re: Tools for code analysis
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Hi Anatole,
this is does not exclude each other. The direct integration offers
support during 'local' development while sonar will help us to see our
progress.
Am 29.11.14 15:03, schrieb Anatole Tresch:
> I would prefer using sonarcube. We can get a free build account from them
> (aka nemo.sonarcube.org)..
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Tools for code analysis
Posted by Anatole Tresch <at...@gmail.com>.
I would prefer using sonarcube. We can get a free build account from them
(aka nemo.sonarcube.org)..
Oliver B. Fischer <o....@swe-blog.net> schrieb am Sa., 29. Nov. 2014
um 14:51:
> Dear all, before touching the whole build I would like to hear your
> opinion on the integration of tool support for code analysis in our build
> chain.
>
> I would like to integrate the following tools in our build chain:
>
> - Findbugs
> - Checkstyle
> - jQassistant
>
> jQassistant is a quite new tool. It allows to import a code basis ( also
> Maven POMs) into Neo4j and to validate custom constraints expressed as
> graph query.
>
> To ensure a fast build they must be triggered by a setting a property or a
> Maven profile. Later we can decide to have hard constraints which must be
> fullfilled for a release.
>
> Wdyt?
>
> Best,
> Oliver
>
> Von meinem iPhone gesendet