Sonar doesn't work with paths with spaces in them

[Charles (Ted) Wise]

I'm calling Sonar from Hudson using the Sonar plug-in.  The path to the Maven 2 POM has spaces in it.  Sonar isn't quoting or escaping the path and Maven is getting confused due to the spaces in the path.  Is there a workaround for handling this?

Unfortunately I didn't setup the SCM structure and can't modify it.

Thanks in advance

[Olivier Gaudin-2]

Hello Charles,

Are you able to run a clean install on the project ?
Have you tried to surround the path with "" ?

Olivier

On Thu, Oct 15, 2009 at 8:38 PM, Charles (Ted) Wise <ctwise@...> wrote:

I'm calling Sonar from Hudson using the Sonar plug-in.  The path to the Maven
2 POM has spaces in it.  Sonar isn't quoting or escaping the path and Maven
is getting confused due to the spaces in the path.  Is there a workaround
for handling this?

Unfortunately I didn't setup the SCM structure and can't modify it.

Thanks in advance
--
View this message in context: http://www.nabble.com/Sonar-doesn%27t-work-with-paths-with-spaces-in-them-tp25913817p25913817.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

[Charles (Ted) Wise]

I don't know how I could surround the path with quotes.  It's being passed from Hudson.  And now that I'm looking at the problem again, it's not Sonar, it's the Hudson Sonar plug-in.

"c:\hudson\tools\Maven_2.2.1\bin\mvn.bat -e -B -f Oracle Fusion Middleware/Code/BPELUtilities/FaultUtilities/pom.xml -Dsonar.host.url=http://localhost:9000 sonar:sonar"

I'll see if I can find support for the plug-in.

Charles (Ted) Wise wrote:

I'm calling Sonar from Hudson using the Sonar plug-in.  The path to the Maven 2 POM has spaces in it.  Sonar isn't quoting or escaping the path and Maven is getting confused due to the spaces in the path.  Is there a workaround for handling this?

Unfortunately I didn't setup the SCM structure and can't modify it.

Thanks in advance

[Olivier Gaudin-2]

Hello Charles,

You are right, the Sonar Hudson Plugin does not cope when there is a space in the path to the pom.xml. I have created SONARPLUGINS-263 to track the issue.
Do you need to be at this level to kick off the job ? If you check out two levels below in the SCM, you would not have the issue, but I guess this is not possible...

Olivier

On Thu, Oct 15, 2009 at 9:44 PM, Charles (Ted) Wise <ctwise@...> wrote:

I don't know how I could surround the path with quotes.  It's being passed
from Hudson.  And now that I'm looking at the problem again, it's not Sonar,
it's the Hudson Sonar plug-in.

"c:\hudson\tools\Maven_2.2.1\bin\mvn.bat -e -B -f Oracle Fusion
Middleware/Code/BPELUtilities/FaultUtilities/pom.xml
-Dsonar.host.url=http://localhost:9000 sonar:sonar"

I'll see if I can find support for the plug-in.

Charles (Ted) Wise wrote:
>
> I'm calling Sonar from Hudson using the Sonar plug-in.  The path to the
> Maven 2 POM has spaces in it.  Sonar isn't quoting or escaping the path
> and Maven is getting confused due to the spaces in the path.  Is there a
> workaround for handling this?
>
> Unfortunately I didn't setup the SCM structure and can't modify it.
>
> Thanks in advance
>

--

View this message in context: http://www.nabble.com/Sonar-doesn%27t-work-with-paths-with-spaces-in-them-tp25913817p25914826.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

[Charles (Ted) Wise]

Much appreciated.  We're not using a "standard" SCM.  It lets you check out a sub path but doesn't appear to let you "clip" the top of the path.  I'll look into it though.

Olivier Gaudin-2 wrote:

Hello Charles,

You are right, the Sonar Hudson Plugin does not cope when there is a space
in the path to the pom.xml. I have created
*SONARPLUGINS-263<http://jira.codehaus.org/browse/SONARPLUGINS-263>
* to track the issue.
Do you need to be at this level to kick off the job ? If you check out two
levels below in the SCM, you would not have the issue, but I guess this is
not possible...

Olivier