[ANN] sonar-maven-plugin 2.1

[Simon Brandhof]

Hi,

The Mojo team is pleased to announce the release of the sonar-maven-plugin
version 2.1.

This plugin allows to inspect code with SonarQube.

http://mojo.codehaus.org/sonar-maven-plugin/

To get this update, simply specify the version in your project's plugin
configuration:

 org.codehaus.mojo
sonar-maven-plugin 2.1


This new version adds the support of Maven 3.1. Note that upgrading to
SonarQube 3.7 is required to benefit from Maven 3.1. Older versions of
SonarQube are still supported when using Maven 3.0.x.


http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12430&version=18062

Enjoy,

The Mojo team.

-- Simon

[ANN] Sonar Maven Plugin 1.0 and 2.0 Released

[Simon Brandhof]

The Mojo team is pleased to announce the final releases of the Sonar Maven
Plugin. This plugin handles code inspection with
Sonar
.

Release 1.0 supports Maven 2 and release 2.0 is for Maven 3. This
document
explains
how to fix the plugin version in pom files.
http://mojo.codehaus.org/sonar-maven-plugin

*Release Notes*

   - Bug
  - [MSONAR-5] - Incorrect URL constructed in ServerMetadata
   - Improvement
  - [MSONAR-9] - Remove the dependency on commons-io
  - [MSONAR-8] - Fix potential conflicts with Sonar plugins by removing the
  dependency on commons-lang

Enjoy,

The Mojo team.

[ANN] Sonar Maven Plugin 2.0-beta-1

[Simon Brandhof]

Hi,

The Mojo team is pleased to announce the release of the Sonar Maven
Plugin version 2.0-beta-1. It adds compatibility with Maven 3 when
using Sonar 2.4.

You can see more about the plugin at:
http://mojo.codehaus.org/sonar-maven-plugin/

Release notes :
 - [MOJO-1545] support Maven 3.

Enjoy,
Simon Brandhof

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Sonar mojo 1.0-beta-2

[Simon Brandhof]

gMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115)
>
>
>
>
> 14.09.2010 13:00, Aleksey Didik пишет:
>
>   Hello.
>>
>> Could anyone tell me the difference between
>> org.codehaus.*mojo*::sonar-maven-plugin and
>> org.codehaus.*sonar*::sonar-maven-plugin?
>>
>> Looks like I have lost a little.
>>
>> Thanks,
>> Aleksey.
>>
>>
>> 13.09.2010 19:24, Simon Brandhof пишет:
>>
>>> The Mojo team is pleased to announce the release of Sonar Maven Plugin,
>>> version 1.0-beta-2.
>>> It makes configuration easier when using a repository manager like
>>> Archiva
>>> or Nexus. Indeed no additional settings are required anymore ! Let's
>>> remind
>>> that the version 1.0-beta-1 needs to declare a mirror in maven settings.
>>>
>>> This improvement requires Sonar 2.2+. It is automatically disabled when
>>> using sonar 2.1 or less. Upgrading to this version should be automatic if
>>> the shortcut "mvn sonar:sonar" is used.
>>>
>>> Simon Brandhof
>>>
>>>
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: [ANN] Sonar mojo 1.0-beta-2

[Simon Brandhof]

Hi Aleksey,

The mojo is a simple bootstrap over the org.codehaus.sonar maven plugin. End
users should execute the first one. The latter is for internal use. The goal
is to simplify the maven command, indeed the mojo version does not change
when sonar is upgraded.

To sum up : you just have to focus on the command "mvn
org.codehaus.mojo:sonar-maven-plugin:1.0-beta-2:sonar" or on its shortcut
"mvn sonar:sonar". It works for any versions of sonar.

This is explained in this post :
http://www.sonarsource.org/we-had-a-dream-mvn-sonarsonar/

Regards
Simon

On Tue, Sep 14, 2010 at 11:00 AM, Aleksey Didik  wrote:

>  Hello.
>
> Could anyone tell me the difference between
> org.codehaus.*mojo*::sonar-maven-plugin and
> org.codehaus.*sonar*::sonar-maven-plugin?
>
> Looks like I have lost a little.
>
> Thanks,
> Aleksey.
>
>
> 13.09.2010 19:24, Simon Brandhof пишет:
>
>  The Mojo team is pleased to announce the release of Sonar Maven Plugin,
>> version 1.0-beta-2.
>> It makes configuration easier when using a repository manager like Archiva
>> or Nexus. Indeed no additional settings are required anymore ! Let's
>> remind
>> that the version 1.0-beta-1 needs to declare a mirror in maven settings.
>>
>> This improvement requires Sonar 2.2+. It is automatically disabled when
>> using sonar 2.1 or less. Upgrading to this version should be automatic if
>> the shortcut "mvn sonar:sonar" is used.
>>
>> Simon Brandhof
>>
>>
>

[ANN] Sonar mojo 1.0-beta-2

[Simon Brandhof]

The Mojo team is pleased to announce the release of Sonar Maven Plugin,
version 1.0-beta-2.
It makes configuration easier when using a repository manager like Archiva
or Nexus. Indeed no additional settings are required anymore ! Let's remind
that the version 1.0-beta-1 needs to declare a mirror in maven settings.

This improvement requires Sonar 2.2+. It is automatically disabled when
using sonar 2.1 or less. Upgrading to this version should be automatic if
the shortcut "mvn sonar:sonar" is used.

Simon Brandhof

[ANN] Cobertura Maven Plugin 2.4 released

[Simon Brandhof]

The Mojo team is pleased to announce the release of the Cobertura Maven
Plugin, version 2.4.

Documentation on the plugin can be found here:
http://mojo.codehaus.org/cobertura-maven-plugin/

Release Notes

** Bug
* [MCOBERTURA-49] - Fails if JRE is not on System Path
* [MCOBERTURA-67] - mvn cobertura:cobertura class loader problem
* [MCOBERTURA-98] - Trivial typos in CommandLineArguments and
CoberturaReportMojo javadocs
* [MCOBERTURA-105] - AbstractCoberturaTestCase hasn't been upgraded to
cobertura 1.9.2

** Improvement
* [MCOBERTURA-113] - Upgrade to cobertura 1.9.3
* [MCOBERTURA-120] - Update to Cobertura 1.9.4.1
* [MCOBERTURA-122] - Upgrade plexus-utils version to 2.0.2

** New Feature
* [MCOBERTURA-85] - Configuration for different report encodings (other
than UTF-8)

** Task
* [MCOBERTURA-111] - Missing url tag in pom.xml


--
Simon Brandhof

[ANN] Cobertura Maven Plugin 2.3

[Simon Brandhof]

The Mojo team is pleased to announce the release of the Cobertura
Maven Plugin 2.3.
http://mojo.codehaus.org/cobertura-maven-plugin/.

Release notes :

** Bug
* [MCOBERTURA-88] - Cobertura runs mess up project classpath
* [MCOBERTURA-96] - Jar classpath ordering issue during test execution

** Improvement
* [MCOBERTURA-81] - Add support for i18n to report mojo
* [MCOBERTURA-100] - Add metrics to the xml report generated by
the goal dump-datafile
* [MCOBERTURA-104] - Upgrade to Cobertura 1.9.2

More details can be found at
http://jira.codehaus.org/browse/MCOBERTURA/fixforversion/13926.

Regards
The Mojo team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Sonar maven plugin 1.0-beta-1 released

[Simon Brandhof]

The Mojo team is pleased to announce the first beta-release of Sonar maven
plugin.

This plugin allows to analyse sources and extract measures to Sonar, an
open-source platform to manage code quality.
See http://mojo.codehaus.org/sonar-maven-plugin for details.

Have fun

Re: problems mirroring repo1.maven.org

[Simon BRANDHOF]

We fixed permissions too late. Files access is now forbidden (like
http://repo1.maven.org/maven2/ch/hortis/sonar/sonar-maven-plugin/1.0.1/sonar-maven-plugin-1.0.1.pom).
It's very embarrassing for us. Could you reexecute the synchronization
please ?

Thanks
Simon

On Nov 28, 2007 12:47 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote:

> fixed the permissions in the main repo, it will take some hours to
> propagate.
> hortis.ch people need to fix the permissions on their side
>
> On Nov 28, 2007 7:29 PM, Stephen Connolly
> <[EMAIL PROTECTED]> wrote:
> > I'm getting the following errors while rsyncing repo1.maven.org
> >
> > Any idea how to fix these?
> >
> > rsync -v -t -l -r --exclude **/.svn/ --exclude .bak --exclude **/CVS/
> > mirrors.ibiblio.org::maven2 /var/www/repo1.maven.org
> >
> >
> >
> >  -
> >
> >  Welcome to the ibiblio.org mirrored software server!
> >
> >
> >
> >  Note that the 'gnuwww' module was recently removed
> >
> >  per discussion with the volunteers running gnu.org.
> >
> >  Please go there if you wish to continue mirroring
> >
> >  their web site. In its stead we are now offering
> >
> >  the GNU Alpha archive.
> >
> >  -
> >
> >
> >
> >
> >
> > receiving file list ... rsync: opendir
> > "/ch/hortis/sonar/sonar-commons/1.0" (in maven2) failed: Permission
> > denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-commons/1.0.1" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-maven-plugin/1.0" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-maven-plugin/1.0.1" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar/1.0" (in maven2) failed:
> > Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar/1.0.1" (in maven2) failed:
> > Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/db-maven-plugin/1.0" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/db-maven-plugin/1.0.1" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-application/1.0" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-application/1.0.1" (in maven2)
> > failed: Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-core/1.0" (in maven2) failed:
> > Permission denied (13)
> >
> > rsync: opendir "/ch/hortis/sonar/sonar-core/1.0.1" (in maven2) failed:
> > Permission denied (13)
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>

Re: reactor

[Simon BRANDHOF]

You must define the maven namespace into the root node of maven.xml :



Cheers,
Simon
http://www.xp-swiss.org

On Apr 11, 2005 4:20 PM, Bahaa Nasrallah <[EMAIL PROTECTED]> wrote:
> hi,
> in my maven.xml i have
> 
>   includes="**/project.xml"
>excludes=""
>banner="Building"
>goals="Complete"
>ignoreFailures="false"/>
> 
> 
> in the command line i try to run "maven buildAll"
> and i get :
> Fatal Error [line 73, row 33]: The prefix "maven" for element "maven:reactor" 
> is
>  not bound.
> 
> what's wrong?
> 
> Thanks in advance
> 
> -----
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
Simon BRANDHOF
Hortis - La rencontre de l'Agilité et de l'Open-source
www.xp-suisse.org
www.hortis.ch

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a practical multiproject build

[Simon BRANDHOF]

Hello,

You can filter the subprojects on which you want to call a goal by
adding the following on the root maven.xml :


 
 

For your example, you should have :


 
 

In your case the subprojects should have the same version number. So I
think that you can set the version (SNAPSHOT) on the root POM
(project.xml) and remove it from subprojects. I hope it will resolve
your problem...

Simon

For the problem
On Apr 11, 2005 12:10 PM, Bahaa Nasrallah <[EMAIL PROTECTED]> wrote:
> I have exactly the smae problem, can anybody who knows how to solve
> this problem reply?
> 
> thanks,
> Bahaa
> 
> On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE
> <[EMAIL PROTECTED]> wrote:
> > I've been working with multiproject for a couple of days, so while I'm
> > not exactly an expert, I feel reasonably confident with the following
> > questions.
> >
> > Basically, I'd like to end up with 1 step to deploying only changes to a
> > web application.  Here's my directory structure:
> >
> > /project
> >/application
> >project.xml
> >...
> >/webClient
> >project.xml
> >...
> >project.xml
> >  ...
> >
> > As I understand it, I need to run multiproject:something from the
> > /project directory, to "build" the multiproject.  Then, I'd like to run
> > jboss:deploy-exploded-warfile from the /webClient directory.  How can I
> > bundle all of this into one goal within /project/maven.xml?  Something
> > like:
> >
> > The other thing I'm wondering is how manage the dependencies as
> > SNAPSHOTs.  For instance, since /webClient depends on /application, I'm
> > guessing that I should have something like this in
> > /webClient/project.xml:
> >
> >
> >project
> >application
> >SNAPSHOT
> >jar
> >
> >true
> >
> >
> >
> > And in /application/project.xml:
> >
> >SNAPSHOT
> >
> > Additionally, /webClient/project.xml has:
> >
> >SNAPSHOT
> >
> > Then, when I cut a release, I would replace SNAPSHOT with whatever
> > version I'm releasing.
> >
> > Since I'll be actively developing both modules at once, they should be
> > SNAPSHOTs right?  Currently, I'm having difficulty getting multiproject
> > to handle SNAPSHOT dependencies.  It always tries to get the dependency
> > from the remote repository despite the fact that the project SNAPSHOT is
> > part of the multiproject.
> >
> > Does this make sense?
> >
> > Thanks,
> >
> > Dave
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
Simon BRANDHOF
Hortis - La rencontre de l'Agilité et de l'Open-source
www.xp-suisse.org
www.hortis.ch

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]