Re: Git or Mercurial
On Sonar side : +1 for Git (pretty well tested) +0 for Mercurial (known open issue with the Sonar SCM Activity plugin : http://jira.codehaus.org/browse/SONARPLUGINS-1157) Freddy Mallet www.SonarSource.org www.SonarSource.com On Mon, Jul 4, 2011 at 1:51 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Git > > On 4 July 2011 12:27, Peter Horlock wrote: > > Hi! > > > > We are planning to move from SVN to either GIT or Mercurial. > > What would you recommend using? > > Which has the better Maven / Eclipse / Sonar Support? > > > > Thanks, > > > > Peter > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Setting custom varaibles
Here is a simple way to do that :
1 - You can set any property directly into the Maven command line :
mvn sonar:sonar -DsrcDirectory=/vol/myProject/src -DbinDirectory=...
2- You can retrieve those values into your pom.xml file :
${srcDirectory}
${binDirectory}
regards,
Freddy Mallet
www.SonarSource.com
Sonar.codehaus.org
http://twitter.com/FreddyMallet
On Sat, Mar 13, 2010 at 3:14 PM, swaroopgr wrote:
>
> Ah! No I can't. That's our default build env! I can't decide! :)
>
> Any other ideas to get this working?
>
>
>
> Maven User-2 wrote:
> >
> > Pull the trigger - modularize and move completely to maven 2.
> >
> > On Mar 12, 2010, at 8:05 PM, swaroopgr wrote:
> >
> >>
> >> Here's why:
> >>
> >> I'm setting up sonar - a tool for code quality analysis. The way
> >> sonar is
> >> run is:
> >>
> >> "mvn sonar:sonar"
> >>
> >> I'm using ANT to build my project. However, sonar requires a dummy
> >> pom.xml
> >> file to trick it into saying it's a maven project. Then, Sonar will
> >> go and
> >> descend into all the directories and complete static code analysis.
> >>
> >> In my case, I need only specific directories to be analysed by
> >> Sonar. Hence,
> >> I simply list these directories and feed it into the pom.xml file's
> >> property. This will allow sonar to analyse only
> >> those
> >> modules.
> >>
> >> Hence, I somehow need to figure out how I can feed these files one
> >> by one
> >> into pom.xml and call mvn each time.
> >>
> >>
> >>
> >>
> >>
> >> Baptiste MATHUS wrote:
> >>>
> >>> Hi,
> >>>
> >>> First question: why do you need to do this?
> >>>
> >>> Maven defines strong conventions principles over config. So doing
> >>> what you
> >>> say seems quite uncommon. So you've got three solutions:
> >>> * if the project can be cleanly refactored to be built, with clear
> >>> deps
> >>> and
> >>> so on => the way to go
> >>> * if those source directories comes from a special process (say
> >>> generation),
> >>> then maybe the way to go is more writing a maven plugin that will
> >>> do what
> >>> you need cleanly (writing a maven plugin is very simple). To help
> >>> answer
> >>> this question, I guess you'll have to explain your need a bit more.
> >>> * combine ant-run plugin/buildhelper should help do the trick, but
> >>> this
> >>> would be like using ant to compile when developing under eclipse
> >>>
> >>> Cheers
> >>>
> >>> 2010/3/12 swaroopgr
> >>>
> >>>>
> >>>> I'm need to use custom variables in maven. Here's what I do:
> >>>>
> >>>> Run the "ls" command in the current directory. For each directory
> >>>> listed,
> >>>> I
> >>>> want to add the name in pom.xml's $DirectoryName
> >>>> property and run mvn. If there's a way to set
> >>>> name /
> >>>> value
> >>>> pairs during mvn invocation, that would be best. If not, what's
> >>>> the best
> >>>> way
> >>>> to do this?
> >>>> --
> >>>> View this message in context:
> >>>>
> http://old.nabble.com/Setting-custom-varaibles-tp27881131p27881131.html
> >>>> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>>>
> >>>>
> >>>> ---
> >>>> --
> >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Baptiste MATHUS - http://batmat.net
> >>> Sauvez un arbre,
> >>> Mangez un castor !
> >>>
> >>>
> >>
> >> --
> >> View this message in context:
> >> http://old.nabble.com/Setting-custom-varaibles-tp27881131p27884743.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Setting-custom-varaibles-tp27881131p27887572.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
[ANN] Sonar 1.12 Released
The Sonar Team is pleased to announce the 8th and last major Sonar release of the year. Around 60 improvements and bug fixes are contained in this new version and the main features are : * Ability to manage authentication and authorization by project * Ability to ignore violations with the new ‘//NOSONAR’ comment. This is a very simple and generic way to eliminate false positive generated for instance by Findbugs or any kind of rules engine. * Highlighted code syntax, because code is not just a bunch of plain black text To get more information : http://sonar.codehaus.org/downloads/ To see Sonar in action : http://nemo.sonarsource.org Enjoy, - The Sonar team Freddy Mallet www.SonarSource.com Sonar.codehaus.org http://twitter.com/FreddyMallet
Re: How-to implement Code Quality Analysis on multiple Maven Projects?
Hi Christian and Barrie, FYI, I've just deployed on Nemo (http://nemo.sonarsource.org) a Sonar Views plugin in a Beta version (this will be a commercial SonarSource plugin). This plugin allows to create any kind of aggregation of technical Maven projects. For instance you can group projects by application, applications by team, teams by service, etc ... I've created three views on Nemo ( http://nemo.sonarsource.org/plugins/home/views) and one of them is the "Forges" view where all projects are grouped by forge (Apache, Codehaus, SourceForge, ...). On the dashboard of the "Forges" view ( http://nemo.sonarsource.org/project/index/Forges), you can see that there are 7 795 000 physical lines under quality control, 64 842 unit tests, unit tests require 5h11mn to be executed, etc. All classical Sonar services keep on working on this view : TimeMachine, Violations drilldown, Hotspots, etc. This is currently the ultimate solution to manage big aggregation trees with hundreds of Maven projects. regards, Freddy -------- Freddy Mallet www.SonarSource.com Sonar.codehaus.org http://twitter.com/FreddyMallet On Tue, Oct 6, 2009 at 8:17 AM, Barrie Treloar wrote: > On Tue, Oct 6, 2009 at 4:05 PM, Christian Breuer > wrote: > > > > org.codehaus.mojo > > build-helper-maven-plugin > > 1.1 > > > > > > add-source > > generate-sources > > > > add-source > > > > > > > > [YOUR SOURCE DIRECTORY 2] > > [YOUR SOURCE DIRECTORY 3] > > > > > > > > > > > > > > > http://docs.codehaus.org/display/SONAR/Collect+data#Collectdata-NonMavenprojects%28sonarlightmode%29 > > > > best regards > > > Wunderful > > Thanks. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How-to implement Code Quality Analysis on multiple Maven Projects?
Hi Ralf, FYI, the Sonar Core and most underlying Maven Quality plugins are compatible with the use of the Maven Build Helper Plugin but this is not the case of the Maven Checkstyle plugin : http://jira.codehaus.org/browse/MCHECKSTYLE-70. Freddy Freddy Mallet www.SonarSource.com Sonar.codehaus.org http://twitter.com/FreddyMallet On Wed, Sep 30, 2009 at 6:56 AM, ifsNabble wrote: > > The analysis is done by Sonar which takes all the configured reports and > the > source code. > Based on the compiled source the JDepend metrics are computed, based on > Cobertura report (created by maven plugin) the code coverage is computed > and > so on... > > Regarding your classpath hint: > I found another Maven plugin (build-helper-maven-plugin) which does > something like that. You can configure different source folders within this > plugin. > Maybe this can be a somehow generic way to do the task without > copying&pasting code from one project to another. > > Our layout is > SVN - trunk - projectA - src - main - java > SVN - trunk - projectB - src - main - java > ... > > When placing a pom.xml in > SVN - trunk - pom.xml (above all other projects) > I ´m able to define with the maven-helper-plugin some source folders like > that: > > org.codehaus.mojo > build-helper-maven-plugin > 1.1 > > > add-source > generate-sources > > add-source > > > > projcetA/src/main/java/ > projectB/src/main/java/ > > > > > > > Maybe that works!? > A colleague of mine will find it out. > > > Quintin Beukes-2 wrote: > > > > OK, I understand. > > > > Of all those software systems you mentioned. Which one of them does > > the actual analysis? doesn't it have a feature to specify more > > classpaths? > > > > Quintin Beukes > > > > > > > > > > -- > View this message in context: > http://www.nabble.com/How-to-implement-Code-Quality-Analysis-on-multiple-Maven-Projects--tp25658865p25675029.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How-to implement Code Quality Analysis on multiple Maven Projects?
Hi Ralf, You're touching a quite interesting subject as some quality metrics are partially or even totally wrong in some cases when analyzing all Maven projects in isolation. This is particularly true when dealing with Robert C. Martin metrics collected for instance with JDepends library. Indeed, Afferent and Efferent Coupling values can greatly change when you analyze the sources of a Maven module (let's say an API) without taking into account all the Maven modules which depend on it. This can be also useful when you're looking for dead public methods or looking for copy/paste between Maven modules. I haven't yet any solution to solve this issue but, at least, I share your need. Freddy On Tue, Sep 29, 2009 at 12:34 PM, ifsNabble wrote: > > It´s quite simple: > Let´s say you have a class A which is a central class in your application. > And you have 5 Maven projects that are using the class A. > > If you do code analysis on Project 1 you will see that the class A is used > by one class in project 1 - because you have only the project 1 in you > focus. > So you won´t assume that class a could be an important central class, > because you don´t know the code of the other projects. > > So my approach is to focus every project in my application. > In my example you will then copy all the code of Project 1, Project 2 ... > and Project 5 into one folder and analyze it together. > Then you will see that class A is used by many, many classes from all the > projects. And you will know that refactoring class A isn´t dead easy, > because now you have the overview - which you don´t have when focussing > only > a single project. > > Ralf > > to see which classes are using another class you have to have the code of > both. > If you have the classes in different Maven projects you > > > > Quintin Beukes-2 wrote: > > > > I don't have experience with this. Why exactly does all code need to > > be together? > > > > Quintin Beukes > > > > > > > > On Tue, Sep 29, 2009 at 10:38 AM, ifsNabble > > wrote: > >> > >> Hi Quintin, > >> > >> I´m starting automatic build in Hudson with Maven target "mvn compile". > >> Then all tests are run and with Sonar-Plugin the code quality is anlyzed > >> and > >> published in Sonar. > >> The quality metrics rely on JUnit (-> Surefire), PMD, Cobertura etc. and > >> some specialties where object coupling, depth of inheritance tree etc. > is > >> computed. > >> And for these special metrics I need all code together during > >> compilation. > >> > >> Ralf > >> > >> > >> Quintin Beukes-2 wrote: > >>> > >>> Yes, writing an ant script that merges projects into a temporary place > >>> is an ugly solution. > >>> > >>> What are you using for the code quality analysis? > >>> > >>> Quintin Beukes > >>> > >>> > >>> > >>> On Tue, Sep 29, 2009 at 10:24 AM, ifsNabble > >>> wrote: > > Hi all! > > I´m stuck with following problem: > > My Project consists of about 150 Maven projects. All of them are > somehow > dependent on each other. > I´m able to build and analyze code quality for every single project. > But to analyze special metrics I need all source code together in one > folder. And there´s my problem. > > I could create a stupid dummy ant script that copies every code from > /src/main/java to the common source folder. And then I start analyzing > this. > But that´s not really what I want. Apart from that I do need a new > pom.xml > for the new all-embracing project. And then I´m at the point where I > have > to > copy/paste the source code from the single projects to the "big" > project. > > I thought about using module for solving my problem, but I don´t know > if > that suits my needs? > > I´m using Eclipse and m2eclipse-Plugin, Hudson as build tool and Sonar > as > code quality analyzer. > Our platform is Windows. > > Does anyone have some suggestions or best practices for my problem? > I´m sure I´m not the first one facing such problems. > > The main pre-conditions for the solution are: > - I don´t want to change the structure of my projects (e.g. merge some > projects together) > - I´d like to use as many native Maven tools as possible (plugins, > techniques like modules, ...) and avoid using handmade solutions like > copy&paste or writing ant scripts > > Thanks already! > -- > View this message in context: > > http://www.nabble.com/How-to-implement-Code-Quality-Analysis-on-multiple-Maven-Projects--tp25658865p25658865.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > >>> > >>> --
Re: Deprecating and banning artifacts with repository metadata
Hi, FYI I've created a ticket few months ago to create such Sonar plugin : http://jira.codehaus.org/browse/SONARPLUGINS-41. This Sonar plugin could work like this : 1 - Accept a text list of prohibited dependencies. For instance : libGroupeId1:libArtifactId1:[libScope1]:[libType1]:(,libVersion1] libGroupeId2:libArtifactId2:[libScope2]:[libType2]:(,libVersion2] 2 - Automatically configure and launch the Maven dependency plugin ( http://maven.apache.org/plugins/maven-dependency-plugin/) to dump the dependency tree in a report file 3 - Read the report file, look for dependencies which could match the prohibited ones and insert those violations in the Sonar DB I'll glad to support anyone interested by writing such plugin. Freddy -------- Freddy Mallet www.SonarSource.com Sonar.codehaus.org http://twitter.com/FreddyMallet On Fri, Sep 11, 2009 at 11:00 PM, Jim Sellers wrote: > Sounds useful to me. > > We were going to build a similar plugin - but the plan for it to be a sonar > plugin rather than a maven plugin. > > Jim > > > On Fri, Sep 11, 2009 at 10:23 AM, Ben Lidgey >wrote: > > > > > It sounds like it could be useful, but perhaps with a warning as there > are > > maintenance projects applying bug fixes to existing projects that may not > > want to update older components to avoid too many changes. > > > > Ben > > > > > > On 10/09/2009 22:03, "Wendy Smoak" wrote: > > > > A group I work with had a requirement to be able to deprecate and ban > > old versions of their artifacts. The dev team is very large and > > simply sending out an email telling everyone not to use version 1.0 of > > some artifact won't work. The team needed a way to warn and/or > > enforce that the old version is no longer supported and should not (or > > must not) be used. > > > > I think they started out writing a rule for the Enforcer plugin, but > > at some point it turned into a separate plugin. (There was a concern > > about teams simply re-configuring the Enforcer plugin to get around > > the rules.) > > > > In the repository, they have a versions-metadata.xml file sitting next > > to the maven-metadata.xml file. The plugin examines all the > > dependencies in the build and looks for the versions-metadata.xml > > file to see if it needs to warn or fail. > > > > They're considering contributing the plugin and are wondering whether > > it sounds useful to the general Maven community before they start > > wading through the corporate legal stuff that would be necessary to > > make that happen. > > > > Does it sound like something you might use? Let me know if you want > > more details on it, or perhaps one of the devs that's involved will > > chime in. > > > > Thanks, > > -- > > Wendy > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > E-Mail : blid...@movenetworks.com > > __ > > Move Networks UK > > Enterprise House > > Navigation Park > > Abercynon > > CF45 4SN > > t: +44 (0)8445 460100 > > f: +44 (0)8445 460200 / (0)1443 742 568 > > w: www.movenetworks.com > > > > >
Re: skipping plugin execution on a module in a multi-modules context
Hi Christophe,
When launching the "mvn sonar:sonar" command on your multi-modules project,
you just have to add the following Sonar property
"-Dsonar.skippedModules=${module_artifact_to_exclude}" and you'll get what
you want.
Hope it helps,
Freddy
--------
Freddy Mallet
www.SonarSource.com
Sonar.codehaus.org
http://twitter.com/FreddyMallet
On Wed, Jun 17, 2009 at 1:36 PM, christophe domas <
christophe.do...@gmail.com> wrote:
> Hi,
> I have a multi-modules project. One of these modules generates some source
> code (from xsd, wsdl, etc) but I don't want to execute some plugins on this
> module (checkstyle, pmd, sonar, etc).
> In general, is it possible to skip plugin execution on a particuliar module
> in a multi-modules project ?
>
> Thanks
>
Re: Using multiple source dirs
Hi Karthik,
Please switch to the Sonar user mailing list [1] in order to get the support
you need.
In few words, you can analyze a non-maven project which has multiple source
directories defined. But, as Kamlesh said, there is currently a limitation :
this mode is not compatible with findbugs, so you can't activate findbugs
rules on those projects.
Hope it helps,
Freddy
[1] - http://sonar.codehaus.org/support/
Freddy Mallet
www.SonarSource.com
Sonar.codehaus.org
http://twitter.com/FreddyMallet
On Tue, May 12, 2009 at 8:30 AM, wrote:
> Hi Kamlesh,
>
> But the link below claims that the support for multiple source dir
> projects(non maven) has been enabled recently. Any thoughts?
>
> http://docs.codehaus.org/display/SONAR/Analyzing+Java+Projects
>
> Thanks
> Karthik
>
>
>
>
>
> -Original Message-
> From: Kamlesh Sangani [mailto:xkamle...@yahoo.com]
> Sent: Tuesday, May 12, 2009 11:54 AM
> To: Maven Users List
> Subject: Re: Using multiple source dirs
>
> multiple source directories configuration does not work with non-maven
> project. see http://jira.codehaus.org/browse/SONAR-623
>
>
>
>
> From: "karthikeyan.sivanant...@wipro.com"
>
> To: users@maven.apache.org
> Sent: Monday, May 11, 2009 11:01:53 PM
> Subject: Using multiple source dirs
>
> Hi all,
>
> I'm trying to use sonar light with my non maven project. When I do a mvn
> clean install, I get the following error. I've pasted my pom.xml after
> the error. I'm using mvn 2.1.0, java 1.5 and sonar 1.7. Any help is
> highly appreciated
>
> [INFO]
>
> [INFO] Building OME_SM
> [INFO]task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error configuring:
> org.apache.maven.plugins:maven-resources-plugin. Reas
> n: ERROR: Cannot override read-only parameter: resources in goal:
> resources:res
> urces
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch [INFO]
>
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Mon May 11 17:58:31 IST 2009 [INFO] Final Memory:
> 7M/13M [INFO]
>
>
>
>
>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
> 4.0.0
>
> WiproTechnologies
>
> OME_SM
>
> OME_SM
>
> 6.0
>
>
>
> ${basedir}/target/sources
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-compiler-plugin
>
>
>
> 1.5
>
> 1.5
>
>
>
> **/*.*
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-resources-plugin
>
> 2.3
>
>
>
> ${basedir}/target/sources
>
>
>
>
>
> ${basedir}/sm_viking/src_release
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> true
>
>
>
>
>
>
>
> thanks!
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
>
>
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended re
[ANNOUNCE] Sonar 1.5 Released
The Sonar team is pleased to announce the release of Sonar 1.5 Sonar is a quality management platform that transparently orchestrates well known tools such as Checkstyle, PMD, Findbugs, JavaNCSS, Clover and Cobertura. Sonar provides the ability to get an insight of the health of projects portfolio, to zoom in on the metrics of a project, to drill down to modules, packages and ultimately sources and to go back in time in order to monitor the trends.* * Sonar integrates seamlessly the maven tools ecosystem. The latest release is now available here : - http://sonar.codehaus.org/downloads/ You can take a tour of latest features by looking at "sonar 1.5 in screenshots" : - http://sonar.codehaus.org/sonar-15-in-screenshots/ If you have any questions, please consult: - the web site: http://sonar.codehaus.org - the sonar-user mailing list: http://sonar.codehaus.org/support/ Thanks, The Sonar team
[ANN] Sonar 1.1 Released : Quality Management Dashboard
The Sonar team is pleased to announce the release of Sonar 1.1. Sonar is a new Open Source (LGPL) Quality Management Dashboard hosted by Codehaus to monitor java projects. If you only work on few java projects, we highly encourage people to take a look or keep using great Open Source tools like Maven Dashboard, XRadar and QALab but if you want to keep control on 10, 50, 100 or more java projects, Sonar could be a more suitable solution to fit enterprise's needs. The particularity of Sonar is to aggregate all quality data in a central database. This database is populated through a Maven plugin which doesn't required any change to your pom file. Take a look at http://sonar.hortis.ch to get a very quick idea of the current functionalities or challenge our 2 minutes installation guide if you want to get more. Sonar is sponsored by Hortis, a Swiss IT company based in Geneva and specialized in agile methodologies Enjoy, -- The Sonar team
