[mojo-dev] [jira] (MSONAR-118) Unable to determine structure of project

2015-04-27 Thread Wesley Connor (JIRA)
Title: Message Title










 

 Wesley Connor commented on an issue











 






  Re: Unable to determine structure of project 










More testing of this has revealed that I can successfully run the sonar:sonar command from a folder cu But if i made a copy of that folder 'cu2' and run sonar:sonar again it fails with the above error.  This seems to indicate that it is not a project error but something in the plugin












   

 Add Comment











 













 Mojo's Sonar Maven Plugin /  MSONAR-118



  Unable to determine structure of project 







 Running following steps from command line  mvn clean install - OK  mvn sonar:sonar -  [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.5:sonar (default-cli) on project reactor-all: Unable to determine structure of project. Probably you use Maven Advanced Reactor Options with a broken tree of modules   It may be possible to post the ...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MSONAR-118) Unable to determine structure of project

2015-04-27 Thread Julien HENRY (JIRA)
Title: Message Title










 

 Julien HENRY commented on an issue











 






  Re: Unable to determine structure of project 










Please provide a sample project to reproduce the issue.












   

 Add Comment











 













 Mojo's Sonar Maven Plugin /  MSONAR-118



  Unable to determine structure of project 







 Running following steps from command line  mvn clean install - OK  mvn sonar:sonar -  [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.5:sonar (default-cli) on project reactor-all: Unable to determine structure of project. Probably you use Maven Advanced Reactor Options with a broken tree of modules   It may be possible to post the ...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MSONAR-118) Unable to determine structure of project

2015-04-27 Thread Wesley Connor (JIRA)
Title: Message Title










 

 Wesley Connor commented on an issue











 






  Re: Unable to determine structure of project 










Thanks for your response It would be very very difficult to produce a sample project as there is code security at stake,  is there no debugging you can suggest I do to try and find the problem?












   

 Add Comment











 













 Mojo's Sonar Maven Plugin /  MSONAR-118



  Unable to determine structure of project 







 Running following steps from command line  mvn clean install - OK  mvn sonar:sonar -  [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.5:sonar (default-cli) on project reactor-all: Unable to determine structure of project. Probably you use Maven Advanced Reactor Options with a broken tree of modules   It may be possible to post the ...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MCOBERTURA-205) Banned Specified Repositories documentation example doesn't work

2015-04-27 Thread JIRA
Title: Message Title










 

 Jakub Boche?ski created an issue











 






 Mojo's Cobertura Maven Plugin /  MCOBERTURA-205



  Banned Specified Repositories documentation example doesn't work 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 27/Apr/15 8:18 AM




Priority:

  Blocker




Reporter:

 Jakub Boche?ski










First the example 



  
http://repo1/*
  


is not even valid XML. After correcting the unclosed tags one gets


[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce-environment) on project super-pom: Unable to parse configuration of mojo org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce for parameter bannedRepositories: Cannot create instance of interface org.apache.maven.enforcer.rule.api.EnforcerRule


I have also tried 



	
		
			http://repo1/*
		
	



and 



	
		
			http://repo1/*
		
	



 

[mojo-dev] [jira] (MCOBERTURA-205) Banned Specified Repositories documentation example doesn't work

2015-04-27 Thread JIRA
Title: Message Title










 

 Jakub Boche?ski commented on an issue











 






  Re: Banned Specified Repositories documentation example doesn't work 










Sorry, filled this under wrong project by mistake - can somebody move this?












   

 Add Comment











 













 Mojo's Cobertura Maven Plugin /  MCOBERTURA-205



  Banned Specified Repositories documentation example doesn't work 







 First the example {code}      http://repo1/*    {code}  is not even valid XML. After correcting the unclosed tags one gets  {code}[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MCOBERTURA-205) Banned Specified Repositories documentation example doesn't work

2015-04-27 Thread JIRA
Title: Message Title










 

 Jakub Boche?ski commented on an issue











 






  Re: Banned Specified Repositories documentation example doesn't work 










On second try I was able to make this work with 




	
		
			http://repo1/*
		
	



On second try, but the examples in docs are still wrong (and the listed parameter "banRepositories" is also misleading)












   

 Add Comment











 













 Mojo's Cobertura Maven Plugin /  MCOBERTURA-205



  Banned Specified Repositories documentation example doesn't work 







 First the example {code}      http://repo1/*    {code}  is not even valid XML. After correcting the unclosed tags one gets  {code}[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












--

[mojo-dev] [jira] (MSONAR-118) Unable to determine structure of project

2015-04-27 Thread Julien HENRY (JIRA)
Title: Message Title










 

 Julien HENRY commented on an issue











 






  Re: Unable to determine structure of project 










You can remove all code. I'm only interested in structure of the multimodule project (parent/child relationship, pom configuration). And if you think even pom.xml may contain sensitive information feel free to send the reproducer to me privately.












   

 Add Comment











 













 Mojo's Sonar Maven Plugin /  MSONAR-118



  Unable to determine structure of project 







 Running following steps from command line  mvn clean install - OK  mvn sonar:sonar -  [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.5:sonar (default-cli) on project reactor-all: Unable to determine structure of project. Probably you use Maven Advanced Reactor Options with a broken tree of modules   It may be possible to post the ...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [RESULT][VOTE] SonarQube Maven plugin 2.6

2015-04-27 Thread Julien HENRY
The vote has passed by lazy consensus. I'll continue with the release.

++
Julien
  De : Julien HENRY 
 À : "d...@sonar.codehaus.org" ; 
"u...@sonar.codehaus.org" ; "dev@mojo.codehaus.org" 
 
 Envoyé le : Vendredi 24 avril 2015 17h09
 Objet : [mojo-dev] [VOTE] SonarQube Maven plugin 2.6
   
Hi,

I would like to release version 2.6 of sonar-maven-plugin.

2 issues have been solved:


* [MSONAR-113] - Feed property sonar.junit.reportsPath
* [MSONAR-117] - Feed properties for Java test classpath

These two changes are required to use/test new features of upcoming SQ Java 
plugin 3.2.

Staging Repository:
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-1176

SCM Tag:
http://svn.codehaus.org/mojo/tags/sonar-maven-plugin-2.6/

[ ] +1
[ ] +0
[ ] -1

The vote is open for 72 hours and will succeed by lazy consensus.


++

Julien

-
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




  

[mojo-dev] [jira] (MTAGLIST-71) New option to exclude resources from validation

2015-04-27 Thread Roman Ivanov (JIRA)
Title: Message Title










 

 Roman Ivanov created an issue











 






 Mojo's Taglist Maven Plugin /  MTAGLIST-71



  New option to exclude resources from validation 










Issue Type:

  Improvement




Affects Versions:


 2.4




Assignee:


 Unassigned




Created:


 27/Apr/15 6:13 PM




Priority:

  Major




Reporter:

 Roman Ivanov










please create an option to allow ignore validation over resource files. example - http://checkstyle.sourceforge.net/taglist.html
we use TODO in our testing files (at resources https://github.com/checkstyle/checkstyle/blob/master/src/test/resources/com/puppycrawl/tools/checkstyle/InputSimple.java ), and now I have no ability to make Taglist report clean.
or please share any other way to avoid that validation. you can test you changes by running "mvn clean site -Dlinkcheck.skip=true" on our project https://github.com/checkstyle/checkstyle












   

 Add Comment







[mojo-dev] [jira] (MTAGLIST-69) Broken xref links

2015-04-27 Thread Roman Ivanov (JIRA)
Title: Message Title










 

 Roman Ivanov commented on an issue











 






  Re: Broken xref links 










verified, it works fine.












   

 Add Comment











 













 Mojo's Taglist Maven Plugin /  MTAGLIST-69



  Broken xref links 







 During generating linkcheck report I've faced problem that taglist plugin generates broken xref links   Example of my current report: http://alexkravin.github.io/testproject/taglist.html   There're with links to xref sources such as:  http://alexkravin.github.io/testproject/xref/com/MyClass.html#17   As you see this link won't redirect you to proper li...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MTAGLIST-71) New option to exclude resources from validation

2015-04-27 Thread Roman Ivanov (JIRA)
Title: Message Title










 

 Roman Ivanov commented on an issue











 






  Re: New option to exclude resources from validation 










kind of workaround:




	  true
  
















   

 Add Comment











 













 Mojo's Taglist Maven Plugin /  MTAGLIST-71



  New option to exclude resources from validation 







 please create an option to allow ignore validation over resource files.  example - http://checkstyle.sourceforge.net/taglist.html   we use TODO in our testing files (at resources https://github.com/checkstyle/checkstyle/blob/master/src/test/resources/com/puppycrawl/tools/checkstyle/InputSimple.java ), and now I have no ability to make Taglist report clea...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[mojo-dev] [jira] (MTAGLIST-69) Broken xref links

2015-04-27 Thread Karl Heinz Marbaise (JIRA)
Title: Message Title










 

 Karl Heinz Marbaise closed an issue as Fixed











 







Veryfied by Aleksey Nesterenko. Thanks for checking it.









 Mojo's Taglist Maven Plugin /  MTAGLIST-69



  Broken xref links 










Change By:

 Karl Heinz Marbaise




Resolution:

 Fixed




Assignee:

 Karl Heinz Marbaise




Status:

 Open Closed












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email