Nabble - Sonar user

Re: Problems building war

2009-11-08T06:33:24Z

Hi John,

That's clearly a good idea, I've created ticket http://jira.codehaus.org/browse/SONAR-1261.

Thanks

Freddy

On Fri, Nov 6, 2009 at 6:15 PM, John Klingler <jfklingler@...> wrote:

Removing the ANT_HOME environment variable did the trick. I didn't even think about it since build-war.bat is calling ant in the internal ant 1.7 distribution. The ant.bat however looks for the ANT_HOME environment variable, which was pointing my 1.6.5 distribution. So the bundled ant 1.7 is only used if you don't have ANT_HOME defined (or it's already pointing at 1.7+ distribution). I modified the build-war script to force use of the bundled ant and it seems to work:

set ORIG_ANT_HOME=%ANT_HOME%
set ANT_HOME=%CD%\apache-ant-1.7.0

call apache-ant-1.7.0\bin\ant

set ANT_HOME=%ORIG_ANT_HOME%
set ORIG_ANT_HOME=

On Fri, Nov 6, 2009 at 10:17 AM, Olivier Gaudin <gaudol@...> wrote:

Hello John,

I would expect you need ant 1.7+.

Olivier

On Fri, Nov 6, 2009 at 5:02 PM, John Klingler <jfklingler@...> wrote:
Same result. I tried it again without adding any plugins or changing any configuration - same result. I do have Ant 1.6.5 installed on the machine but sonar appears to be using it's own local version. I'll try removing ant from the system path (WinXP if it matters) to see if that makes any difference.

On Fri, Nov 6, 2009 at 2:40 AM, Olivier Gaudin <gaudol@...> wrote:
Hello John,

Looks very strange. Can you start from scratch ? Unzip the 1.11.1 in a fresh directory, copy any plugin / extension you need, copy your sonar.property and run the command again.

Olivier

On Thu, Nov 5, 2009 at 3:51 PM, John Klingler <jfklingler@...> wrote:
Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:
Buildfile: build.xml

clean:

war:

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web
   [copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data
   [copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

   [copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions
   [copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes
   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

   [war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED
C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:


   [war] Building war: C:\sonar-1.11.1\war\sonar.war
   [war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)
   [echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

Re: Problems building war

2009-11-06T09:15:03Z

Removing the ANT_HOME environment variable did the trick. I didn't even think about it since build-war.bat is calling ant in the internal ant 1.7 distribution. The ant.bat however looks for the ANT_HOME environment variable, which was pointing my 1.6.5 distribution. So the bundled ant 1.7 is only used if you don't have ANT_HOME defined (or it's already pointing at 1.7+ distribution). I modified the build-war script to force use of the bundled ant and it seems to work:

set ORIG_ANT_HOME=%ANT_HOME%

set ANT_HOME=%CD%\apache-ant-1.7.0

call apache-ant-1.7.0\bin\ant

set ANT_HOME=%ORIG_ANT_HOME%

set ORIG_ANT_HOME=

On Fri, Nov 6, 2009 at 10:17 AM, Olivier Gaudin <gaudol@...> wrote:

Hello John,

I would expect you need ant 1.7+.

Olivier

On Fri, Nov 6, 2009 at 5:02 PM, John Klingler <jfklingler@...> wrote:
Same result. I tried it again without adding any plugins or changing any configuration - same result. I do have Ant 1.6.5 installed on the machine but sonar appears to be using it's own local version. I'll try removing ant from the system path (WinXP if it matters) to see if that makes any difference.

On Fri, Nov 6, 2009 at 2:40 AM, Olivier Gaudin <gaudol@...> wrote:
Hello John,

Looks very strange. Can you start from scratch ? Unzip the 1.11.1 in a fresh directory, copy any plugin / extension you need, copy your sonar.property and run the command again.

Olivier

On Thu, Nov 5, 2009 at 3:51 PM, John Klingler <jfklingler@...> wrote:
Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:
Buildfile: build.xml

clean:

war:

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web
   [copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data
   [copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

   [copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions
   [copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes
   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

   [war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED
C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:


   [war] Building war: C:\sonar-1.11.1\war\sonar.war
   [war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)
   [echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT

2009-11-06T08:19:52Z

Cool. Thanks for creating the ticket.

Olivier

On Fri, Nov 6, 2009 at 4:52 PM, Doug Douglass <douglass.doug@...> wrote:

Thanks Olivier! Your diagnosis of both problems was spot on.

One of the effected projects was not a maven multi-project, so not effected by SONAR-1118. Running a new, trunk analysis fixed that project. For the other, multi-module project, running the analysis after a separate mvn clean package fixed that one.

Created SONAR-1260.

Doug

On Thu, Nov 5, 2009 at 1:27 PM, Olivier Gaudin <gaudol@...> wrote:

Hello Doug,

Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?

On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?

Olivier

On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.

A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:

"uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"

I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.

The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.

Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.

Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.

The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?

Other info that may be relavant:

* using postgres 8.3.8
* CentOS 5.3

Any help is appreciated.

TIA,
Doug

[1] http://old.nabble.com/hotspots-and-clouds-can%27t-be-loaded-%28still-loading%29-%28sonar-1.11%29-to25868775.html

[2] http://localhost:9000/api/resources?resource=563&metrics=function_complexity&scopes=FIL&depth=-1&limit=5&format=json&callback=callback5

[3] http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-Upgradeguide

Re: Problems building war

2009-11-06T08:17:11Z

Hello John,

I would expect you need ant 1.7+.

Olivier

On Fri, Nov 6, 2009 at 5:02 PM, John Klingler <jfklingler@...> wrote:

Same result. I tried it again without adding any plugins or changing any configuration - same result. I do have Ant 1.6.5 installed on the machine but sonar appears to be using it's own local version. I'll try removing ant from the system path (WinXP if it matters) to see if that makes any difference.

On Fri, Nov 6, 2009 at 2:40 AM, Olivier Gaudin <gaudol@...> wrote:
Hello John,

Looks very strange. Can you start from scratch ? Unzip the 1.11.1 in a fresh directory, copy any plugin / extension you need, copy your sonar.property and run the command again.

Olivier

On Thu, Nov 5, 2009 at 3:51 PM, John Klingler <jfklingler@...> wrote:
Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:
Buildfile: build.xml

clean:

war:

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web
   [copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data
   [copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

   [copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions
   [copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes
   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

   [war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED
C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:


   [war] Building war: C:\sonar-1.11.1\war\sonar.war
   [war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)
   [echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

Re: Problems building war

2009-11-06T08:02:33Z

Same result. I tried it again without adding any plugins or changing any configuration - same result. I do have Ant 1.6.5 installed on the machine but sonar appears to be using it's own local version. I'll try removing ant from the system path (WinXP if it matters) to see if that makes any difference.

On Fri, Nov 6, 2009 at 2:40 AM, Olivier Gaudin <gaudol@...> wrote:

Hello John,

Looks very strange. Can you start from scratch ? Unzip the 1.11.1 in a fresh directory, copy any plugin / extension you need, copy your sonar.property and run the command again.

Olivier

On Thu, Nov 5, 2009 at 3:51 PM, John Klingler <jfklingler@...> wrote:
Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:
Buildfile: build.xml

clean:

war:

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web
   [copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data
   [copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

   [copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions
   [copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes
   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

   [war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED
C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:


   [war] Building war: C:\sonar-1.11.1\war\sonar.war
   [war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)
   [echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

--
John Klingler
jfklingler@...

Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT

2009-11-06T07:52:22Z

Thanks Olivier! Your diagnosis of both problems was spot on.

One of the effected projects was not a maven multi-project, so not effected by SONAR-1118. Running a new, trunk analysis fixed that project. For the other, multi-module project, running the analysis after a separate mvn clean package fixed that one.

Created SONAR-1260.

Doug

On Thu, Nov 5, 2009 at 1:27 PM, Olivier Gaudin <gaudol@...> wrote:

Hello Doug,

Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?

On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?

Olivier

On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.

A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:

"uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"

I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.

The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.

Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.

Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.

The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?

Other info that may be relavant:

* using postgres 8.3.8
* CentOS 5.3

Any help is appreciated.

TIA,
Doug

[1] http://old.nabble.com/hotspots-and-clouds-can%27t-be-loaded-%28still-loading%29-%28sonar-1.11%29-to25868775.html

[2] http://localhost:9000/api/resources?resource=563&metrics=function_complexity&scopes=FIL&depth=-1&limit=5&format=json&callback=callback5

[3] http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-Upgradeguide

Re: Problems building war

2009-11-06T00:40:56Z

Hello John,

Looks very strange. Can you start from scratch ? Unzip the 1.11.1 in a fresh directory, copy any plugin / extension you need, copy your sonar.property and run the command again.

Olivier

On Thu, Nov 5, 2009 at 3:51 PM, John Klingler <jfklingler@...> wrote:

Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:
Buildfile: build.xml

clean:

war:

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web
   [copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

   [mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data
   [copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

   [copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions
   [copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes
   [copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

   [war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED
C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:


   [war] Building war: C:\sonar-1.11.1\war\sonar.war
   [war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)
   [echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT

2009-11-05T12:27:09Z

Hello Doug,

Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?

On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?

Olivier

On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:

Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.

A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:

"uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"

I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.

The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.

Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.

Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.

The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?

Other info that may be relavant:

* using postgres 8.3.8
* CentOS 5.3

Any help is appreciated.

TIA,
Doug

[1] http://old.nabble.com/hotspots-and-clouds-can%27t-be-loaded-%28still-loading%29-%28sonar-1.11%29-to25868775.html

[2] http://localhost:9000/api/resources?resource=563&metrics=function_complexity&scopes=FIL&depth=-1&limit=5&format=json&callback=callback5

[3] http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-Upgradeguide

clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT

2009-11-05T08:33:32Z

Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.

A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:

"uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"

I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.

The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.

Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.

Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.

The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?

Other info that may be relavant:

* using postgres 8.3.8

* CentOS 5.3

Any help is appreciated.

TIA,

Doug

[1] http://old.nabble.com/hotspots-and-clouds-can%27t-be-loaded-%28still-loading%29-%28sonar-1.11%29-to25868775.html

[2] http://localhost:9000/api/resources?resource=563&metrics=function_complexity&scopes=FIL&depth=-1&limit=5&format=json&callback=callback5

[3] http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-Upgradeguide

Sonar view plugin improvement

2009-11-05T08:16:08Z

hi

I am testing the view plugin.
It is a good plugin, but it could be improved by adding for each view the number of projects that composed the view.

Easier to do I think !

Fabrice

Re: Re: java.lang.NoClassDefFoundError: org/apache/maven/model/Reporting with empty local maven repository

2009-11-05T07:45:59Z

On Thu, Nov 5, 2009 at 6:18 AM, Larry Shatzer, Jr. <larrys@...> wrote:
> Yes, all my projects exhibit it. I'll see if I can find a simple pom
> that does not have my companies corporate pom in it that experiences
> it. They are fairly simple poms (pretty much just dependencies, and a
> few simple configs, no reporting being run, or other stuff). I planned
> on today trying to remove various things to narrow it down. Such as
> take Nexus out of the equation, and have a simple pom that did not
> have a parent pom, nor any dependencies.

I have eliminated Nexus (at least from having it proxy Sonar for its
plugins) with a <mirrorOf>*,!sonar</mirrorOf> and adding a mirror with
an id of sonar set to the sonar instance. I saw it download the sonar
stuff from the sonar instance in the output.

While trying something else unrelated, I got this stack trace: (added
a clirr report, and ran a site generation)

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org/apache/maven/artifact/versioning/VersionRange
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError:
org/apache/maven/artifact/versioning/VersionRange
at org.codehaus.mojo.clirr.AbstractClirrMojo.getComparisonArtifact(AbstractClirrMojo.java:408)
at org.codehaus.mojo.clirr.AbstractClirrMojo.canGenerate(AbstractClirrMojo.java:577)
at org.codehaus.mojo.clirr.ClirrReport.canGenerateReport(ClirrReport.java:342)
at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:177)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

A second run fixed it. It looks like it might not be related to Sonar,
but something else.

I just tried to replicate it on another box, (and various versions of
maven from 2.0.10 up to latest)... On the bamboo box, it always fails,
while the other box it works fine.

Both are running "1.5.0_09" of java (I have replicated this with never
versions of java as well)

Bamboo box is Red Hat Enterprise Linux Server release 5.2 (Tikanga)

The working box is Red Hat Enterprise Linux AS release 4 (Nahant Update 3)

Both are a VM on vmware.

I am puzzled even more now...

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Problems building war

2009-11-05T06:51:20Z

Hello. I'm having trouble building the WAR for Sonar 1.11.1 though this has been an issue for me since 1.10. My java version is 1.6.0_11 although I don't think that's necessarily related to this issue.

The output of the build-war script is:

Buildfile: build.xml

clean:

war:

[mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web

[copy] Copying 1518 files to C:\sonar-1.11.1\war\build\sonar-web

[mkdir] Created dir: C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\data

[copy] Copying 24 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\lib

[copy] Copying 27 files to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

[copy] Copied 9 empty directories to 1 empty directory under C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes\extensions

[copy] Copying 1 file to C:\sonar-1.11.1\war\build\sonar-web\WEB-INF\classes

[war] Building war: C:\sonar-1.11.1\war\sonar.war

BUILD FAILED

C:\sonar-1.11.1\war\build.xml:38: webxml attribute is required

Total time: 1 minute 28 seconds

Line 38 is "<war destfile="sonar.war">". If I change it to "<war destfile="sonar.war" webxml="sonar-web\WEB-INF\web.xml">", then the build finishes successfully, but I have the following messages:

[war] Building war: C:\sonar-1.11.1\war\sonar.war

[war] Warning: selected war files include a WEB-INF/web.xml which will be

ignored (please use webxml attribute to war task)

[echo] sonar.war is built.

If I deploy the WAR, it works just fine despite the warning. Changing line 38 to "<war destfile="sonar.war" webxml="build\sonar-web\WEB-INF\web.xml">" yields the same result. Changing it to "<war destfile="sonar.war" webxml="WEB-INF\web.xml">" gives me the error "Deployment descriptor: C:\sonar-1.11.1\war\WEB-INF\web.xml does not exist.", which it doesn't - I was just covering the bases.

Has anyone else seen this? I found 0 results on the mail archives and JIRA for anything containing "webxml". Unless I'm missing something, it seems like a trivial fix.

--
John Klingler
jfklingler@...

Re: Re: java.lang.NoClassDefFoundError: org/apache/maven/model/Reporting with empty local maven repository

2009-11-05T05:18:21Z

Yes, all my projects exhibit it. I'll see if I can find a simple pom
that does not have my companies corporate pom in it that experiences
it. They are fairly simple poms (pretty much just dependencies, and a
few simple configs, no reporting being run, or other stuff). I planned
on today trying to remove various things to narrow it down. Such as
take Nexus out of the equation, and have a simple pom that did not
have a parent pom, nor any dependencies.

On Thu, Nov 5, 2009 at 5:41 AM, Simon Brandhof <simon.brandhof@...> wrote:

> Hi guys,
>
> From Benjamin Bentmann point of view, changing the scope of maven
> dependencies does not fix the problem [1]. Moreover I can't reproduce the
> issue with Maven 2.2.0/2.2.1, Java 5/6 and Sonar 1.10/1.11 when setting the
> parameter -Dmaven.repo.local=/path/to/empty/dir
>
> Larry, do you have the issue on all your projects ? Could you send a sample
> of pom please ?
>
> Regards,
> Simon
>
> [1] http://jira.codehaus.org/browse/MOJO-1450
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Tomcat error deploying Sonar 1.11.1

2009-11-05T04:49:45Z

I'm afraid it's not so simple to change the version of xstream directly from the distribution. You'll have to wait SONAR-1258 [1] to be resolved. It's planned for release 1.12.

Regards
Simon
[1] http://jira.codehaus.org/browse/SONAR-1258

Re: Re: java.lang.NoClassDefFoundError: org/apache/maven/model/Reporting with empty local maven repository

2009-11-05T04:41:35Z

Hi guys,

From Benjamin Bentmann point of view, changing the scope of maven dependencies does not fix the problem [1]. Moreover I can't reproduce the issue with Maven 2.2.0/2.2.1, Java 5/6 and Sonar 1.10/1.11 when setting the parameter -Dmaven.repo.local=/path/to/empty/dir

Larry, do you have the issue on all your projects ? Could you send a sample of pom please ?

Regards,
Simon

[1] http://jira.codehaus.org/browse/MOJO-1450

Re: Sonar build fails when multiple repositories are used

2009-11-04T12:04:27Z

Excellent !

Thanks for your patience.

Olivier

On Wed, Nov 4, 2009 at 6:59 PM, Lars Fischer <lfischer@...> wrote:

Olivier Gaudin schrieb:

The last one seems to be gone this time. Can you try again cleaning up your local and nexus repo for org/codehaus/mojo first ?

I tested again and now I it's working fine.

Great... thank you for fixing! :)

Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-04T09:59:23Z

Olivier Gaudin schrieb:
> The last one seems to be gone this time. Can you try again cleaning up
> your local and nexus repo for org/codehaus/mojo first ?

I tested again and now I it's working fine.

Great... thank you for fixing! :)

Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-04T09:08:43Z

Hello Lars,

The last one seems to be gone this time. Can you try again cleaning up your local and nexus repo for org/codehaus/mojo first ?

Thanks you for your help !

Olivier

On Wed, Nov 4, 2009 at 3:31 PM, Olivier Gaudin <gaudol@...> wrote:

Ok, there still seem to be a snapshot left on the sonatype repo. Bear with me.

Olivier

On Wed, Nov 4, 2009 at 10:03 AM, Lars Fischer <lfischer@...> wrote:
Hello Olivier,

Olivier Gaudin schrieb:

Could you give it an other try as I think it should be fixed now.

I removed all org.codehaus.mojo artefacts from my nexus and the hudson local repository and disabled the "sonatype-snapshot" repository.

Then I tried to execute sonar without setting the version to 1.0-beta-1. This results in the same error:

[INFO]-----------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]------------------------------------------------------------------------
[INFO] Total time: 29 seconds
[INFO] Finished at: Wed Nov 04 09:38:58 CET 2009
[INFO] Final Memory: 17M/34M
[INFO]------------------------------------------------------------------------
channel stopped
ln failed: -1
ln failed: -1
[core] $ /usr/local/tools/hudson/hudson_home/tools/Maven_2_0_9/bin/mvn -e -B -f pom.xml -Dsonar.jdbc.driver=org.apache.derby.jdbc.ClientDriver -Dsonar.jdbc.username=sonar -Dsonar.jdbc.password=sonar -Dsonar.jdbc.url=jdbc:derby://localhost:1527/sonar;create=true -Dsonar.host.url=http://localhost:9080/sonar sonar:sonar
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] snapshot com.ibykus.apx:parent.osgibundle:1.1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO] snapshot com.ibykus.apx:parent:1.1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO] Searching repository for plugin with prefix: 'sonar'.
[INFO] org.codehaus.mojo: checking for updates from public
[INFO] org.codehaus.mojo: checking for updates from public-snapshots
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from public
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from public-snapshots
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from central
[INFO] snapshot org.codehaus.mojo:sonar-maven-plugin:1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO]------------------------------------------------------------------------

[ERROR] BUILD ERROR
[INFO]------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.codehaus.mojo:sonar-maven-plugin

Reason: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
from the specified remote repositories:
public (http://slief116:9080/nexus/content/groups/public),
public-snapshots (http://slief116:9080/nexus/content/groups/public-snapshots)
for project org.codehaus.mojo:sonar-maven-plugin

Using a parent pom with a pluginmanagement setting <version>1.0-beta-1</version>. Sonar is running fine.

Do you expect an other result?
What do I have to change to test your fix?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: source code in source viewer is out of sync

2009-11-04T07:00:37Z

Yes, I am using version 1.9.2 so that must be the issue. Thanks!

Freddy Mallet wrote:

Hi Anita,

Could you confirm that you're not running Sonar 1.11 but a lower version ?
If this is the case, you're facing a purge issue which has been fixed with
http://jira.codehaus.org/browse/SONAR-1085.

regards,
Freddy

On Tue, Nov 3, 2009 at 9:32 PM, anitacita <stout_anita@emc.com> wrote:

>
> After a code change to address some violations listed in sonar, I
> reanalyzed
> my maven project by:
>
> mvn clean install -Dtest=false -DfailIfNoTests=false
> mvn sonar:sonar
>
> However, although some of the data shown in Sonar seems to have updated
> (like the total technical debt), the source code in the source/violation
> viewer displays the out of date source from before my change. Is there a
> way to force this to sync up?
>
> BTW, I also tried clearing my browser cache as well as trying another
> browser.
>
> Thanks!
> Anita
> --
> View this message in context:
> http://old.nabble.com/source-code-in-source-viewer-is-out-of-sync-tp26163577p26163577.html
> Sent from the Sonar user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

Re: Sonar build fails when multiple repositories are used

2009-11-04T06:32:50Z

Hello Nanditha,

Mirrors are not needed at all to run Sonar.

Olivier

On Wed, Nov 4, 2009 at 1:40 PM, nandyiyer <nandussiyer@...> wrote:

Can someone explain why are mirrors needed and how can they be helpful in
this situation ?

Thanks,
Nanditha

nandyiyer wrote:
>
> Hi all ,
>
> I have used mutilple repositories in my pom.xml . As a reason sonar build
> fails for my project .
>
> The error stack is as shown below ...
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.codehaus.mojo:sonar-maven-plugin
>
> Reason: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from
> the repository: Failed to resolve artifact, possibly due to a repository
> list that is not appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
> for project org.codehaus.mojo:sonar-maven-plugin
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving
> version for 'org.codehaus.mojo:sonar-maven-plugin': Unable to read the
> metadata file for artifact 'org.codehaus.mojo:sonar-maven-plugin:pom':
> Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the
> repository: Failed to resolve artifact, possibly due to a repository list
> that is not appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
> for project org.codehaus.mojo:sonar-maven-plugin
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1549)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by:
> org.apache.maven.plugin.version.PluginVersionResolutionException: Error
> resolving version for 'org.codehaus.mojo:sonar-maven-plugin': Unable to
> read the metadata file for artifact
> 'org.codehaus.mojo:sonar-maven-plugin:pom': Error getting POM for
> 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to
> resolve artifact, possibly due to a repository list that is not
> appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
> for project org.codehaus.mojo:sonar-maven-plugin
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveMetaVersion(DefaultPluginVersionManager.java:682)
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:187)
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:179)
> at
> org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
> ... 15 more
> Caused by:
> org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
> Unable to read the metadata file for artifact
> 'org.codehaus.mojo:sonar-maven-plugin:pom': Error getting POM for
> 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to
> resolve artifact, possibly due to a repository list that is not
> appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
> for project org.codehaus.mojo:sonar-maven-plugin
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:299)
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveMetaVersion(DefaultPluginVersionManager.java:673)
> ... 20 more
> Caused by: org.apache.maven.project.ProjectBuildingException: Error
> getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the
> repository: Failed to resolve artifact, possibly due to a repository list
> that is not appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
> for project org.codehaus.mojo:sonar-maven-plugin
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:592)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163)
> ... 22 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException:
> Failed to resolve artifact, possibly due to a repository list that is not
> appropriately equipped for this artifact's metadata.
> org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
>
> from the specified remote repositories:
> flexmojos-repository
> (http://repository.sonatype.org/content/groups/public),
> central (http://repo1.maven.org/maven2)
>
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:221)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
> ... 24 more
>
>
> Can anyone help me regarding this ?
>
> Thanks ,
> Nanditha
>
>

--

View this message in context: http://old.nabble.com/Sonar-build-fails-when-multiple-repositories-are-used-tp26113355p26195614.html

Sent from the Sonar user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-04T06:31:44Z

Ok, there still seem to be a snapshot left on the sonatype repo. Bear with me.

Olivier

On Wed, Nov 4, 2009 at 10:03 AM, Lars Fischer <lfischer@...> wrote:

Hello Olivier,

Olivier Gaudin schrieb:

Could you give it an other try as I think it should be fixed now.

I removed all org.codehaus.mojo artefacts from my nexus and the hudson local repository and disabled the "sonatype-snapshot" repository.

Then I tried to execute sonar without setting the version to 1.0-beta-1. This results in the same error:

[INFO]-----------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]------------------------------------------------------------------------
[INFO] Total time: 29 seconds
[INFO] Finished at: Wed Nov 04 09:38:58 CET 2009
[INFO] Final Memory: 17M/34M
[INFO]------------------------------------------------------------------------
channel stopped
ln failed: -1
ln failed: -1
[core] $ /usr/local/tools/hudson/hudson_home/tools/Maven_2_0_9/bin/mvn -e -B -f pom.xml -Dsonar.jdbc.driver=org.apache.derby.jdbc.ClientDriver -Dsonar.jdbc.username=sonar -Dsonar.jdbc.password=sonar -Dsonar.jdbc.url=jdbc:derby://localhost:1527/sonar;create=true -Dsonar.host.url=http://localhost:9080/sonar sonar:sonar
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] snapshot com.ibykus.apx:parent.osgibundle:1.1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO] snapshot com.ibykus.apx:parent:1.1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO] Searching repository for plugin with prefix: 'sonar'.
[INFO] org.codehaus.mojo: checking for updates from public
[INFO] org.codehaus.mojo: checking for updates from public-snapshots
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from public
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from public-snapshots
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for updates from central
[INFO] snapshot org.codehaus.mojo:sonar-maven-plugin:1.0-SNAPSHOT: checking for updates from public-snapshots
[INFO]------------------------------------------------------------------------

[ERROR] BUILD ERROR
[INFO]------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.codehaus.mojo:sonar-maven-plugin

Reason: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
from the specified remote repositories:
public (http://slief116:9080/nexus/content/groups/public),
public-snapshots (http://slief116:9080/nexus/content/groups/public-snapshots)
for project org.codehaus.mojo:sonar-maven-plugin

Using a parent pom with a pluginmanagement setting <version>1.0-beta-1</version>. Sonar is running fine.

Do you expect an other result?
What do I have to change to test your fix?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-04T04:40:03Z

Can someone explain why are mirrors needed and how can they be helpful in this situation ?

Thanks,
Nanditha

nandyiyer wrote:

Hi all ,

I have used mutilple repositories in my pom.xml . As a reason sonar build fails for my project .

The error stack is as shown below ...

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.codehaus.mojo:sonar-maven-plugin

Reason: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

for project org.codehaus.mojo:sonar-maven-plugin

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving version for 'org.codehaus.mojo:sonar-maven-plugin': Unable to read the metadata file for artifact 'org.codehaus.mojo:sonar-maven-plugin:pom': Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

for project org.codehaus.mojo:sonar-maven-plugin
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1549)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.codehaus.mojo:sonar-maven-plugin': Unable to read the metadata file for artifact 'org.codehaus.mojo:sonar-maven-plugin:pom': Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

for project org.codehaus.mojo:sonar-maven-plugin
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveMetaVersion(DefaultPluginVersionManager.java:682)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:187)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:179)
at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
... 15 more
Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.codehaus.mojo:sonar-maven-plugin:pom': Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

for project org.codehaus.mojo:sonar-maven-plugin
at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200)
at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:299)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveMetaVersion(DefaultPluginVersionManager.java:673)
... 20 more
Caused by: org.apache.maven.project.ProjectBuildingException: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

for project org.codehaus.mojo:sonar-maven-plugin
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:592)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163)
... 22 more
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
flexmojos-repository (http://repository.sonatype.org/content/groups/public),
central (http://repo1.maven.org/maven2)

at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:221)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 24 more

Can anyone help me regarding this ?

Thanks ,
Nanditha

[ANN] Timeline plugin, release 0.1

2009-11-04T03:20:40Z

The new Timeline plugin is a great addition to the TimeMachine service. It benefits from an incredible Google Vizualization component.

Read this blog post for more details : http://sonar.codehaus.org/the-sonar-timeline-plugin-a-great-addition-to-timemachine-service/
Download : http://docs.codehaus.org/display/SONAR/Timeline+Plugin

Enjoy,
Simon

----------------------------------------
Simon Brandhof
SonarSource.com
twitter.com/SonarSource
twitter.com/SimonBrandhof
----------------------------------------

Re: Sonar build fails when multiple repositories are used

2009-11-04T01:03:52Z

Hello Olivier,

Olivier Gaudin schrieb:
> Could you give it an other try as I think it should be fixed now.

I removed all org.codehaus.mojo artefacts from my nexus and the hudson
local repository and disabled the "sonatype-snapshot" repository.

Then I tried to execute sonar without setting the version to 1.0-beta-1.
This results in the same error:

[INFO]-----------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]------------------------------------------------------------------------
[INFO] Total time: 29 seconds
[INFO] Finished at: Wed Nov 04 09:38:58 CET 2009
[INFO] Final Memory: 17M/34M
[INFO]------------------------------------------------------------------------
channel stopped
ln failed: -1
ln failed: -1
[core] $ /usr/local/tools/hudson/hudson_home/tools/Maven_2_0_9/bin/mvn
-e -B -f pom.xml -Dsonar.jdbc.driver=org.apache.derby.jdbc.ClientDriver
-Dsonar.jdbc.username=sonar -Dsonar.jdbc.password=sonar
-Dsonar.jdbc.url=jdbc:derby://localhost:1527/sonar;create=true
-Dsonar.host.url=http://localhost:9080/sonar sonar:sonar
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] snapshot com.ibykus.apx:parent.osgibundle:1.1.0-SNAPSHOT:
checking for updates from public-snapshots
[INFO] snapshot com.ibykus.apx:parent:1.1.0-SNAPSHOT: checking for
updates from public-snapshots
[INFO] Searching repository for plugin with prefix: 'sonar'.
[INFO] org.codehaus.mojo: checking for updates from public
[INFO] org.codehaus.mojo: checking for updates from public-snapshots
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for
updates from public
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for
updates from public-snapshots
[INFO] artifact org.codehaus.mojo:sonar-maven-plugin: checking for
updates from central
[INFO] snapshot org.codehaus.mojo:sonar-maven-plugin:1.0-SNAPSHOT:
checking for updates from public-snapshots
[INFO]------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.codehaus.mojo:sonar-maven-plugin

Reason: Error getting POM for 'org.codehaus.mojo:sonar-maven-plugin'
from the repository: Failed to resolve artifact, possibly due to a
repository list that is not appropriately equipped for this artifact's
metadata.
org.codehaus.mojo:sonar-maven-plugin:pom:1.0-SNAPSHOT
from the specified remote repositories:
public (http://slief116:9080/nexus/content/groups/public),
public-snapshots
(http://slief116:9080/nexus/content/groups/public-snapshots)
for project org.codehaus.mojo:sonar-maven-plugin

Using a parent pom with a pluginmanagement setting
<version>1.0-beta-1</version>. Sonar is running fine.

Do you expect an other result?
What do I have to change to test your fix?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: Sonar plugin for custom violations

2009-11-04T00:25:50Z

Hey Freddy,

I finally got it working. Here's a round-up of the things I did wrong, just for future reference :

- Create a RulesRepository (and add as extension in the plugin). I guess at startup, Sonar will query this repository and add the new rules to be used (rules definitions, not actual violations). So, creating a 'new Rule(...)' in the Sensor only does not work.

- In the Sensor, a lot of classes can be automatically injected in the constructor (just one line of documentation about this ?). This way, I inject the RulesManager, from which I can get a certain rule to create a violation (rulesManager.getPluginRule(...))

- I forgot to activate the rules in the Sonar profile configuration screen (pretty trivial but easy to forget).

Knowing all this, it's actually pretty easy :-)

Thanks again for the help !

Geert

From: Freddy Mallet [mailto:freddy.mallet@...]
Sent: maandag 2 november 2009 19:56
To: user@...; dev@...
Subject: Re: [sonar-user] Sonar plugin for custom violations

Hi Geert,

What you missed is to declare the rule(s) in a repository with the RulesRepository extension point.

You can have a look at the Taglist plugin which embeds a simple rules repository :

http://svn.codehaus.org/sonar-plugins/trunk/taglist/src/main/java/org/sonar/plugins/taglist/

Hope it helps,
Freddy

On Mon, Nov 2, 2009 at 4:17 PM, Geert Van Damme <GVanDamme@...> wrote:

Hi all,

I'm writing a plugin to report custom violations (Class A may not access class B, to report layering problems in the project).
The code for analyzing the project has already been written, and it generates a simple report in XML (which class, line number, ...)

Now I'm trying to write a plugin to parse the XML and add the violations to Sonar. But before parsing the XML, I'm trying to just add a hard-coded violation to see if this works. I can add measures without any problem (based on the HelloWorld, but with INT instead of string, so I get a tendency as well). But the violations don't seem to show anywhere in the timeline or violations drilldown.

So, my question(s) :
- if the report is already generated (ant build), I suppose I don't need a MavenPluginHandler ?

- Can I do something like this in my Sensor ? :
<--->
...
Rule testRule = new Rule(HelloPlugin.PLUGIN_KEY, "violation_key",
"Test violation !", Iso9126RulesCategories.MAINTAINABILITY,
RulePriority.BLOCKER);
Violation violation = new Violation(repository.getRule(), new JavaFile("some.package.SomeClass"));
Violation.setLineId(20);
Context.saveViolation(violation);
...
<--->

I got the feeling I'm missing something stupid here, as this does't work. The documentation doesn't seem to mention anything about the RulesRepository (which I already tried without success), or any plugin development besides the HelloWorld in fact.

Thanks in advance,
Geert

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Geert Van Damme

Java Developer Consultant

E-mail : GVanDamme@...

Tel : +32
Fax : +32

Isabel NV/S.A.
Keizerinlaan 13-15 Boulevard de l'Impératrice

1000 Brussels - Belgium
RPR Bruxelles / RPM Brussel: BE 0455 530 509

www.isabel.eu www.zoomit.eu

Zoomit is a Registered Trademark of Isabel NV/S.A.
Disclaimer : www.isabel.eu/gps/en/disclaimer/mailing.php

Re: unknown null pointer exception

2009-11-04T00:19:31Z

Not yet sure, but I would not be surprised if this issue was related to http://jira.codehaus.org/browse/SONAR-1118.

2009/11/4 José Arcángel Salazar Delgado <arcangel.salazar@...>

> Hello José,
>
> Can you give a bit more info ?
> - is your project built with Maven ?
> - have you tried with the Sonar Way profile ?
> - can you activate -e option ?
>
> Olivier

I can resolv the issue. The problem is that I miss this configuration in the
pom:

<build>
<sourceDirectory>src</sourceDirectory>
<outputDirectory>bin</outputDirectory>
...
</build>

Is rare, because I have a similar project without these options and works
fine.

Thanks anyway.

>
>
>
> 2009/11/3 José Arcángel Salazar Delgado <arcangel.salazar@...>
>
> > hi,
> >
> > I'm getting null pointer exception from sonar when I create a build using
> > Hudson:
> >
> > + Error stacktraces are turned on.
> >
> > [INFO] Scanning for projects...
> >
> > [INFO] Searching repository for plugin with prefix: 'sonar'.
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [sonar:sonar] (aggregator-style)
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [sonar:sonar]
> >
> > [INFO] Sonar host: http://127.0.0.1:8080/sonar
> >
> > [INFO] Sonar version: 1.11.1
> >
> > [INFO] [sonar-core:internal]
> >
> > [INFO] ------------- Analyse Sistema Servidor Integra GUI...
> >
> > [INFO] Selected quality profile : Sonar way with Findbugs, language=java
> >
> > [INFO] Configure maven plugins...
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [generate-sources]
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [build-helper:add-source {execution: add-source}]
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/Generat
> >ed JUIC files added.
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/src
> > added.
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.JavaSourceImporter
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.AsynchronousMeasuresSensor
> >
> > [INFO] Executing sensor class org.sonar.plugins.findbugs.FindbugsSensor
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [ERROR] BUILD ERROR
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Can not execute Sonar
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Trace
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute
> > Sonar
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:564)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
> >(DefaultLifecycleExecutor.java:493)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLi
> >fecycleExecutor.java:463)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleF
> >ailures(DefaultLifecycleExecutor.java:311)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(D
> >efaultLifecycleExecutor.java:224)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecy
> >cleExecutor.java:143)
> >
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> >
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> >
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> >:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> >mpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:597)
> >
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Can not
> > execute Sonar
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:87)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:65)
> >
> > at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:117)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:539)
> >
> > ... 16 more
> >
> > Caused by: java.lang.NullPointerException
> >
> > at
> > org.sonar.batch.DefaultMavenPluginExecutor.execute(DefaultMavenPluginExec
> >utor.java:45)
> >
> > at
> > org.sonar.batch.core.SensorsExecutor.executeMavenPlugin(SensorsExecutor.j
> >ava:68)
> >
> > at org.sonar.batch.core.SensorsExecutor.execute(SensorsExecutor.java:58)
> >
> > at org.sonar.batch.Batch.executeJobs(Batch.java:91)
> >
> > at org.sonar.batch.Batch.analyse(Batch.java:79)
> >
> > at org.sonar.batch.Batch.start(Batch.java:54)
> >
> > at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
> >
> > at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:82)
> >
> > ... 20 more
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Total time: 13 seconds
> >
> > [INFO] Finished at: Tue Nov 03 04:15:21 CST 2009
> >
> > [INFO] Final Memory: 15M/101M
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > Finished: FAILURE
> >
> > I have 5 projects in hudson, and the others compiles fine.
> >
> > thanks for the help.
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: unknown null pointer exception

2009-11-03T19:25:01Z

> Hello José,
>
> Can you give a bit more info ?
> - is your project built with Maven ?
> - have you tried with the Sonar Way profile ?
> - can you activate -e option ?
>
> Olivier

I can resolv the issue. The problem is that I miss this configuration in the
pom:

<build>
<sourceDirectory>src</sourceDirectory>
<outputDirectory>bin</outputDirectory>
...
</build>

Is rare, because I have a similar project without these options and works
fine.

Thanks anyway.

>
>
>
> 2009/11/3 José Arcángel Salazar Delgado <arcangel.salazar@...>
>
> > hi,
> >
> > I'm getting null pointer exception from sonar when I create a build using
> > Hudson:
> >
> > + Error stacktraces are turned on.
> >
> > [INFO] Scanning for projects...
> >
> > [INFO] Searching repository for plugin with prefix: 'sonar'.
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [sonar:sonar] (aggregator-style)
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [sonar:sonar]
> >
> > [INFO] Sonar host: http://127.0.0.1:8080/sonar
> >
> > [INFO] Sonar version: 1.11.1
> >
> > [INFO] [sonar-core:internal]
> >
> > [INFO] ------------- Analyse Sistema Servidor Integra GUI...
> >
> > [INFO] Selected quality profile : Sonar way with Findbugs, language=java
> >
> > [INFO] Configure maven plugins...
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [generate-sources]
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [build-helper:add-source {execution: add-source}]
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/Generat
> >ed JUIC files added.
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/src
> > added.
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.JavaSourceImporter
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.AsynchronousMeasuresSensor
> >
> > [INFO] Executing sensor class org.sonar.plugins.findbugs.FindbugsSensor
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [ERROR] BUILD ERROR
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Can not execute Sonar
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Trace
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute
> > Sonar
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:564)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
> >(DefaultLifecycleExecutor.java:493)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLi
> >fecycleExecutor.java:463)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleF
> >ailures(DefaultLifecycleExecutor.java:311)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(D
> >efaultLifecycleExecutor.java:224)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecy
> >cleExecutor.java:143)
> >
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> >
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> >
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> >:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> >mpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:597)
> >
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Can not
> > execute Sonar
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:87)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:65)
> >
> > at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:117)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:539)
> >
> > ... 16 more
> >
> > Caused by: java.lang.NullPointerException
> >
> > at
> > org.sonar.batch.DefaultMavenPluginExecutor.execute(DefaultMavenPluginExec
> >utor.java:45)
> >
> > at
> > org.sonar.batch.core.SensorsExecutor.executeMavenPlugin(SensorsExecutor.j
> >ava:68)
> >
> > at org.sonar.batch.core.SensorsExecutor.execute(SensorsExecutor.java:58)
> >
> > at org.sonar.batch.Batch.executeJobs(Batch.java:91)
> >
> > at org.sonar.batch.Batch.analyse(Batch.java:79)
> >
> > at org.sonar.batch.Batch.start(Batch.java:54)
> >
> > at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
> >
> > at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:82)
> >
> > ... 20 more
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Total time: 13 seconds
> >
> > [INFO] Finished at: Tue Nov 03 04:15:21 CST 2009
> >
> > [INFO] Final Memory: 15M/101M
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > Finished: FAILURE
> >
> > I have 5 projects in hudson, and the others compiles fine.
> >
> > thanks for the help.
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: unknown null pointer exception

2009-11-03T19:00:47Z

> Hello José,
>
> Can you give a bit more info ?
> - is your project built with Maven ?
> - have you tried with the Sonar Way profile ?
> - can you activate -e option ?
>
Yes, the proyect is build with maven using Hudson.
Yes, I tried, same result.
The option is alrededy activate. I also use the -X option, but I cannot get
any extra information about the crash.

> Olivier
>
>
>
> 2009/11/3 José Arcángel Salazar Delgado <arcangel.salazar@...>
>
> > hi,
> >
> > I'm getting null pointer exception from sonar when I create a build using
> > Hudson:
> >
> > + Error stacktraces are turned on.
> >
> > [INFO] Scanning for projects...
> >
> > [INFO] Searching repository for plugin with prefix: 'sonar'.
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [sonar:sonar] (aggregator-style)
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [sonar:sonar]
> >
> > [INFO] Sonar host: http://127.0.0.1:8080/sonar
> >
> > [INFO] Sonar version: 1.11.1
> >
> > [INFO] [sonar-core:internal]
> >
> > [INFO] ------------- Analyse Sistema Servidor Integra GUI...
> >
> > [INFO] Selected quality profile : Sonar way with Findbugs, language=java
> >
> > [INFO] Configure maven plugins...
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Building Sistema Servidor Integra GUI
> >
> > [INFO] task-segment: [generate-sources]
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] [build-helper:add-source {execution: add-source}]
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/Generat
> >ed JUIC files added.
> >
> > [INFO] Source directory:
> > /opt/glassfishv3-prelude/.hudson/jobs/silm_gui/workspace/silm_gui/src
> > added.
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.JavaSourceImporter
> >
> > [INFO] Executing sensor class
> > org.sonar.plugins.core.sensors.AsynchronousMeasuresSensor
> >
> > [INFO] Executing sensor class org.sonar.plugins.findbugs.FindbugsSensor
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [ERROR] BUILD ERROR
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Can not execute Sonar
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Trace
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute
> > Sonar
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:564)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
> >(DefaultLifecycleExecutor.java:493)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLi
> >fecycleExecutor.java:463)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleF
> >ailures(DefaultLifecycleExecutor.java:311)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(D
> >efaultLifecycleExecutor.java:224)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecy
> >cleExecutor.java:143)
> >
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> >
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> >
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> >:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> >mpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:597)
> >
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Can not
> > execute Sonar
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:87)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:65)
> >
> > at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:117)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL
> >ifecycleExecutor.java:539)
> >
> > ... 16 more
> >
> > Caused by: java.lang.NullPointerException
> >
> > at
> > org.sonar.batch.DefaultMavenPluginExecutor.execute(DefaultMavenPluginExec
> >utor.java:45)
> >
> > at
> > org.sonar.batch.core.SensorsExecutor.executeMavenPlugin(SensorsExecutor.j
> >ava:68)
> >
> > at org.sonar.batch.core.SensorsExecutor.execute(SensorsExecutor.java:58)
> >
> > at org.sonar.batch.Batch.executeJobs(Batch.java:91)
> >
> > at org.sonar.batch.Batch.analyse(Batch.java:79)
> >
> > at org.sonar.batch.Batch.start(Batch.java:54)
> >
> > at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
> >
> > at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
> >
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMan
> >ager.java:447)
> >
> > at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:82)
> >
> > ... 20 more
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > [INFO] Total time: 13 seconds
> >
> > [INFO] Finished at: Tue Nov 03 04:15:21 CST 2009
> >
> > [INFO] Final Memory: 15M/101M
> >
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > Finished: FAILURE
> >
> > I have 5 projects in hudson, and the others compiles fine.
> >
> > thanks for the help.
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: source code in source viewer is out of sync

2009-11-03T12:59:01Z

Hi Anita,

Could you confirm that you're not running Sonar 1.11 but a lower version ? If this is the case, you're facing a purge issue which has been fixed with http://jira.codehaus.org/browse/SONAR-1085.

regards,
Freddy

On Tue, Nov 3, 2009 at 9:32 PM, anitacita <stout_anita@...> wrote:

After a code change to address some violations listed in sonar, I reanalyzed
my maven project by:

mvn clean install -Dtest=false -DfailIfNoTests=false
mvn sonar:sonar

However, although some of the data shown in Sonar seems to have updated
(like the total technical debt), the source code in the source/violation
viewer displays the out of date source from before my change. Is there a
way to force this to sync up?

BTW, I also tried clearing my browser cache as well as trying another
browser.

Thanks!
Anita
--
View this message in context: http://old.nabble.com/source-code-in-source-viewer-is-out-of-sync-tp26163577p26163577.html
Sent from the Sonar user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

source code in source viewer is out of sync

2009-11-03T12:32:23Z

After a code change to address some violations listed in sonar, I reanalyzed my maven project by:

mvn clean install -Dtest=false -DfailIfNoTests=false
mvn sonar:sonar

However, although some of the data shown in Sonar seems to have updated (like the total technical debt), the source code in the source/violation viewer displays the out of date source from before my change. Is there a way to force this to sync up?

BTW, I also tried clearing my browser cache as well as trying another browser.

Thanks!
Anita

Re: Project links not saveable?

2009-11-03T12:12:47Z

Hello Harald,

Yep, something is not working anymore... I have created a Jira issue : SONAR-1253

Olivier

On Tue, Nov 3, 2009 at 3:19 PM, Goettlicher Harald (AA-DGP/ESI2) <Harald.Goettlicher@...> wrote:

Oh yes, sorry. Mailed too fast. Here it is:

2009.11.03 15:16:23 ERROR rails

NameError (undefined local variable or method `project' for #<ProjectController:0xe68afc>):
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:1253:in `perform_action'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:617:in `call_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-complete-1.3.1.jar!/benchmark.rb:293:in `measure'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/rescue.rb:136:in `perform_action_with_rescue'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:13:in `perform_action_with_caching'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/activerecord-2.2.2/lib/active_record/query_cache.rb:8:in `cache'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:12:in `perform_action_with_caching'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:524:in `process'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:606:in `process_with_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/session_management.rb:134:in `process_with_session_management_support'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:392:in `process'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:183:in `handle_request'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:120:in `dispatch'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:39:in `dispatch'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails_cgi.rb:24:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails.rb:35:in `serve_rails'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails.rb:40:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/jruby/rack/rails.rb:144:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/handler/servlet.rb:17:in `call'
    :1

I guess there is something mixed up with "project" and "projects", because in the user message you also get "go back projects" which doesn't work, because it's "project"...

   Harald

Von: Olivier Gaudin [mailto:gaudol@...]
Gesendet: Dienstag, 3. November 2009 15:02
An: user@...
Betreff: Re: [sonar-user] Project links not saveable?

Hello Harald,

Any error in the log file ?

Olivier

On Tue, Nov 3, 2009 at 2:58 PM, Goettlicher Harald (AA-DGP/ESI2) <Harald.Goettlicher@...> wrote:

Hi,

in Sonar 1.11 i always get the following message when trying to save project links, independent if something was changed or if they are empty or filled out.

We're sorry, but something went wrong.

Please try back in a few minutes and contact support if the problem persists.

go back projects

We have two Sonar instances on different machines and both behave the same way...

Harald

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-03T12:06:59Z

Lars,

Could you give it an other try as I think it should be fixed now.

Thanks

Olivier

On Tue, Nov 3, 2009 at 3:45 PM, Olivier Gaudin <gaudol@...> wrote:

No pb at all Lars. This whole thing is a bit annoying as it gives a bad impression and fixing it is not in our hands...
Anyway, the answer to your question is : absolutely, you should use 1.0-beta-1 as a version.

Olivier

On Tue, Nov 3, 2009 at 3:28 PM, Lars Fischer <lfischer@...> wrote:
Hello Olivier,

I hope you have recognised the smiley. My post wasn't intended as offence.

Olivier Gaudin schrieb:

I would to bring some clarifications as several assumptions have been madehere.

1. http://repository.sonatype.org <http://repository.sonatype.org/> is a repository managed by Sonatype, that aggregates many repository. Those repository can contain anything

2. We only publish releases, not snapshots
3. The latest version of the mojo is 1.0-beta-1 : http://repository.sonatype.org/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/1.0-beta-1/

Having said that, we did publish by mistake a 1.0-snapshot on the 6th of June and this was apparently captured by some repositories. As this snapshot version is more recent than the 1.0-beta-1, if you do not explicitly mention the version it is going to try to download the 1.0-snapshot version and then fails as it does not exist (was removed).

Thank you for the clarification.

I am going to see if I can get it fixed in Sonatype repo. For the time being, I would recommend you set the version of the mojo.

I execute sonar within a hudson ci-build. Can I change the mojo version by using plugin-management / dependency-management in the parent pom of my projects?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-03T06:45:45Z

No pb at all Lars. This whole thing is a bit annoying as it gives a bad impression and fixing it is not in our hands...
Anyway, the answer to your question is : absolutely, you should use 1.0-beta-1 as a version.

Olivier

On Tue, Nov 3, 2009 at 3:28 PM, Lars Fischer <lfischer@...> wrote:

Hello Olivier,

I hope you have recognised the smiley. My post wasn't intended as offence.

Olivier Gaudin schrieb:

I would to bring some clarifications as several assumptions have been madehere.

1. http://repository.sonatype.org <http://repository.sonatype.org/> is a repository managed by Sonatype, that aggregates many repository. Those repository can contain anything

2. We only publish releases, not snapshots
3. The latest version of the mojo is 1.0-beta-1 : http://repository.sonatype.org/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/1.0-beta-1/

Having said that, we did publish by mistake a 1.0-snapshot on the 6th of June and this was apparently captured by some repositories. As this snapshot version is more recent than the 1.0-beta-1, if you do not explicitly mention the version it is going to try to download the 1.0-snapshot version and then fails as it does not exist (was removed).

Thank you for the clarification.

I am going to see if I can get it fixed in Sonatype repo. For the time being, I would recommend you set the version of the mojo.

I execute sonar within a hudson ci-build. Can I change the mojo version by using plugin-management / dependency-management in the parent pom of my projects?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Sonar build fails when multiple repositories are used

2009-11-03T06:28:30Z

Hello Olivier,

I hope you have recognised the smiley. My post wasn't intended as offence.

Olivier Gaudin schrieb:

> I would to bring some clarifications as several assumptions have been
> madehere.
>
> 1. http://repository.sonatype.org <http://repository.sonatype.org/> is a
> repository managed by Sonatype, that aggregates many repository. Those
> repository can contain anything
> 2. We only publish releases, not snapshots
> 3. The latest version of the mojo is 1.0-beta-1 :
> http://repository.sonatype.org/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/1.0-beta-1/
>
> Having said that, we did publish by mistake a 1.0-snapshot on the 6th of
> June and this was apparently captured by some repositories. As this
> snapshot version is more recent than the 1.0-beta-1, if you do not
> explicitly mention the version it is going to try to download the
> 1.0-snapshot version and then fails as it does not exist (was removed).

Thank you for the clarification.

> I am going to see if I can get it fixed in Sonatype repo. For the time
> being, I would recommend you set the version of the mojo.

I execute sonar within a hudson ci-build. Can I change the mojo version
by using plugin-management / dependency-management in the parent pom of
my projects?

Regards,
Lars

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

AW: Project links not saveable?

2009-11-03T06:19:36Z

Oh yes, sorry. Mailed too fast. Here it is:

2009.11.03 15:16:23 ERROR rails

NameError (undefined local variable or method `project' for #<ProjectController:0xe68afc>):
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:1253:in `perform_action'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:617:in `call_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-complete-1.3.1.jar!/benchmark.rb:293:in `measure'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/rescue.rb:136:in `perform_action_with_rescue'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:13:in `perform_action_with_caching'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/activerecord-2.2.2/lib/active_record/query_cache.rb:8:in `cache'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:12:in `perform_action_with_caching'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:524:in `process'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/filters.rb:606:in `process_with_filters'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/session_management.rb:134:in `process_with_session_management_support'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/base.rb:392:in `process'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:183:in `handle_request'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:120:in `dispatch'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/gems/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:39:in `dispatch'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails_cgi.rb:24:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails.rb:35:in `serve_rails'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/adapter/rails.rb:40:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/jruby/rack/rails.rb:144:in `call'
    file:/D:/leo-kpi-root/sonar-1.11/war/sonar-web/WEB-INF/lib/jruby-rack-0.9.4.jar!/rack/handler/servlet.rb:17:in `call'
    :1

I guess there is something mixed up with "project" and "projects", because in the user message you also get "go back projects" which doesn't work, because it's "project"...

Harald

Von: Olivier Gaudin [mailto:gaudol@...]
Gesendet: Dienstag, 3. November 2009 15:02
An: user@...
Betreff: Re: [sonar-user] Project links not saveable?

Hello Harald,

Any error in the log file ?

Olivier

On Tue, Nov 3, 2009 at 2:58 PM, Goettlicher Harald (AA-DGP/ESI2) <Harald.Goettlicher@...> wrote:

Hi,

in Sonar 1.11 i always get the following message when trying to save project links, independent if something was changed or if they are empty or filled out.

We're sorry, but something went wrong.

Please try back in a few minutes and contact support if the problem persists.

go back projects

We have two Sonar instances on different machines and both behave the same way...

Harald

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email