[jira] (MRRESOURCES-64) Mojo: process uses deprecated expression project.build.resources

2012-08-18 Thread SebbASF (JIRA)
SebbASF created MRRESOURCES-64:
--

 Summary: Mojo: process uses deprecated expression 
project.build.resources
 Key: MRRESOURCES-64
 URL: https://jira.codehaus.org/browse/MRRESOURCES-64
 Project: Maven 2.x Remote Resources Plugin
  Issue Type: Bug
Reporter: SebbASF


Updating from 1.2.1 to 1.3 causes Maven builds to report the following:

[WARNING] The parameter expression: 'project.build.resources' used in mojo: 
'process' has been deprecated. Use 'project.resources' instead.

Looks like this was a side-effect of the fix for MRRESOURCES-57, see:

http://svn.apache.org/viewvc/maven/plugins/trunk/maven-remote-resources-plugin/src/main/java/org/apache/maven/plugin/resources/remote/ProcessRemoteResourcesMojo.java?r1=1057005r2=1165423

The offending change seems to be:

@@ -313,7 +313,7 @@
 /**
  * The list of resources defined for the project.
  *
- * @parameter expression=${project.resources}
+ * @parameter default-value=${project.build.resources}
  * @readonly
  * @required


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MDEP-109) Dependency plugin looses file permissions when unpacking or copying artifact items

2012-08-18 Thread Vincent Massol (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306481#comment-306481
 ] 

Vincent Massol commented on MDEP-109:
-

Hi Tim,

Thanks for pinging me. I've tested it an you're right, version 2.5 fixes the 
problem! :)

Thanks again

PS: I'll let you close the issue since I don't know if you want to close it as 
duplicate of the real issue that fixed the issue or not.

 Dependency plugin looses file permissions when unpacking or copying artifact 
 items
 --

 Key: MDEP-109
 URL: https://jira.codehaus.org/browse/MDEP-109
 Project: Maven 2.x Dependency Plugin
  Issue Type: Bug
  Components: copy, copy-dependencies, unpack, unpack-dependencies
Affects Versions: 2.0-alpha-4
Reporter: Vincent Massol
Assignee: Brian Fox

 I have to add the following ugly config in my pom.xml to overcome this:
 {code}
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-antrun-plugin/artifactId
 executions
   execution
 phaseprepare-package/phase
 goals
   goalrun/goal
 /goals
 configuration
   tasks
 !-- Dependency plugin discards file permissions so we need 
 to set them back manually --
 chmod 
 file=${project.build.directory}/dependency/bin/windres perm=ugo+rx/
 chmod file=${project.build.directory}/dependency/bin/ld 
 perm=ugo+rx/
 ...
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-650) Problem with multiple executions of surefire within site plugin 3.0

2012-08-18 Thread Kristian Rosenvold (JIRA)
Kristian Rosenvold created MSITE-650:


 Summary: Problem with multiple executions of surefire within site 
plugin 3.0
 Key: MSITE-650
 URL: https://jira.codehaus.org/browse/MSITE-650
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Kristian Rosenvold


There is a test project attached to SUREFIRE-905 that has a total of 4 
executions of surefire, with different configuration for each.

When running mvn clean install inside this project, surefire gets executed 4 
times as expected. When running mvn site only the first execution gets run, 
the last three get stopped by the configuration-checksum in surefire, 
indicating they get executed with the *same* configuration as the default 
execution.  (Surefire creates a SHA1 hash of all the mojo parameters to avoid 
re-running the same configuration, which is why I conclude the three executions 
get the same configuration as the default config)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-888) reportFormatplain/reportFormat should inject \n after per-method test line items in console files

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-888.
---

   Resolution: Fixed
Fix Version/s: 2.13.0
 Assignee: Kristian Rosenvold

Fixed in the refactoring of the reporting system in r1374259

 reportFormatplain/reportFormat should inject \n after per-method test 
 line items in console  files
 -

 Key: SUREFIRE-888
 URL: https://jira.codehaus.org/browse/SUREFIRE-888
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: java 1.7.0_05
 maven 3.0.4
Reporter: Andrei Pozolotin
Assignee: Kristian Rosenvold
 Fix For: 2.13.0


 the following pom
 https://github.com/carrot-garden/sql_mybatis-koans/blob/master/pom.xml
 when run like this
 mvn clean verify -P run-test-koans-h2
 produces reports on console like one shown at the bottom;
 but surefire forgets to separate per-method test report entreis with EOL,
 you would expect it to look like this instead:
 learnToQueryViaXmlMapperReturningHashMap(..)  Time elapsed: 1.072 sec
 learnToQueryMapperReturningHashMapWithParameterInput(..)  Time elapsed: 0.005 
 sec
 learnToQueryViaXmlMapperReturningListOfHashMaps(..)  Time elapsed: 0.036 sec
 BTW this used to look OK in the past;
 ---   
   

  T E S T S
   

 ---   
   

 Concurrency config is parallel='none', perCoreThreadCount=true, 
 threadCount=2, useUnlimitedThreads=false  
  
 Running net.thornydev.mybatis.test.koan01.Koan01  
   

 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec   
   

 learnBasicConfigurationSetup(net.thornydev.mybatis.test.koan01.Koan01)  Time 
 elapsed: 0.1 secRunning net.thornydev.mybatis.test.koan02.Koan02  
 
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.113 sec
 learnToQueryViaXmlMapperReturningHashMap(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 1.072 
 seclearnToQueryMapperReturningHashMapWithParameterInput(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 0.005 
 seclearnToQueryViaXmlMapperReturningListOfHashMaps(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 0.036 secRunning net.thornydev.mybatis.test.koan03.Koan03
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec
 learnToQueryViaXmlMapperReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.026 
 seclearnToQueryViaXmlMapperReturningCountryDomainObject(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.008 
 seclearnToQueryViaXmlMapperReturningListOfCountries(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.033 secRunning net.thornydev.mybatis.test.koan04.Koan04
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
 learnToQueryViaXmlMapperReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.02 
 seclearnToQueryViaXmlMapperReturningCountryDomainObject(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.003 
 seclearnToQueryViaXmlMapperReturningListOfCountries(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.017 secRunning net.thornydev.mybatis.test.koan05.Koan05
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.052 sec
 learnToQueryViaMapperClassReturningCountryDomainObject(net.thornydev.mybatis.test.koan05.Koan05)
   Time elapsed: 0.011 
 seclearnToQueryViaMapperClassReturningListOfCountries(net.thornydev.mybatis.test.koan05.Koan05)
   Time elapsed: 0.014 
 seclearnToQueryViaMapperClassReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan05.Koan05)
  

[jira] (SUREFIRE-878) redirectTestOutputToFile is empty when text is written to output too early (SpringJUnit4ClassRunner)

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-878.
---

Resolution: Fixed
  Assignee: Kristian Rosenvold

Fixed with IT in r1374593, thanks for report and testcase!

 redirectTestOutputToFile is empty when text is written to output too early 
 (SpringJUnit4ClassRunner)
 

 Key: SUREFIRE-878
 URL: https://jira.codehaus.org/browse/SUREFIRE-878
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.10, 2.11, 2.12
 Environment: tested on Windows XP + JDK 1.6.29 and Linux (2.6.32) JDK 
 1.6.24, Maven 2.2.1
Reporter: Jakub Berlinski
Assignee: Kristian Rosenvold
Priority: Minor
 Attachments: RedirectTest-output.txt, redirect.zip


 I'm using a trivial test using SpringJUnit4ClassRunner (RedirectTest.java). 
 The test prints a simple message to the standard output. I run the test with 
 mvn test command. 
 When log4j is configured to print some spring execution details (logger set 
 to level INFO) the RedirectTest-output.txt file is empty. 
 To reproduce: 
 unzip redirect.zip file
 run mvn test
 confirm that the file target/surefire-reports/RedirectTest-output.txt is empty
 Optionally: edit pom.xml file, change maven-surefire-plugin version to 2.9 . 
 run mvn test
 confirm that the file target/surefire-reports/RedirectTest-output.txt is not 
 empty. See attached RedirectTest-output.txt captured using 
 maven-surefire-plugin version 2.9. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-878) redirectTestOutputToFile is empty when text is written to output too early (SpringJUnit4ClassRunner)

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold updated SUREFIRE-878:


Fix Version/s: 2.13.0

 redirectTestOutputToFile is empty when text is written to output too early 
 (SpringJUnit4ClassRunner)
 

 Key: SUREFIRE-878
 URL: https://jira.codehaus.org/browse/SUREFIRE-878
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.10, 2.11, 2.12
 Environment: tested on Windows XP + JDK 1.6.29 and Linux (2.6.32) JDK 
 1.6.24, Maven 2.2.1
Reporter: Jakub Berlinski
Assignee: Kristian Rosenvold
Priority: Minor
 Fix For: 2.13.0

 Attachments: RedirectTest-output.txt, redirect.zip


 I'm using a trivial test using SpringJUnit4ClassRunner (RedirectTest.java). 
 The test prints a simple message to the standard output. I run the test with 
 mvn test command. 
 When log4j is configured to print some spring execution details (logger set 
 to level INFO) the RedirectTest-output.txt file is empty. 
 To reproduce: 
 unzip redirect.zip file
 run mvn test
 confirm that the file target/surefire-reports/RedirectTest-output.txt is empty
 Optionally: edit pom.xml file, change maven-surefire-plugin version to 2.9 . 
 run mvn test
 confirm that the file target/surefire-reports/RedirectTest-output.txt is not 
 empty. See attached RedirectTest-output.txt captured using 
 maven-surefire-plugin version 2.9. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-888) reportFormatplain/reportFormat should inject \n after per-method test line items in console files

2012-08-18 Thread Andrei Pozolotin (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306488#comment-306488
 ] 

Andrei Pozolotin commented on SUREFIRE-888:
---

thank you!

 reportFormatplain/reportFormat should inject \n after per-method test 
 line items in console  files
 -

 Key: SUREFIRE-888
 URL: https://jira.codehaus.org/browse/SUREFIRE-888
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: java 1.7.0_05
 maven 3.0.4
Reporter: Andrei Pozolotin
Assignee: Kristian Rosenvold
 Fix For: 2.13.0


 the following pom
 https://github.com/carrot-garden/sql_mybatis-koans/blob/master/pom.xml
 when run like this
 mvn clean verify -P run-test-koans-h2
 produces reports on console like one shown at the bottom;
 but surefire forgets to separate per-method test report entreis with EOL,
 you would expect it to look like this instead:
 learnToQueryViaXmlMapperReturningHashMap(..)  Time elapsed: 1.072 sec
 learnToQueryMapperReturningHashMapWithParameterInput(..)  Time elapsed: 0.005 
 sec
 learnToQueryViaXmlMapperReturningListOfHashMaps(..)  Time elapsed: 0.036 sec
 BTW this used to look OK in the past;
 ---   
   

  T E S T S
   

 ---   
   

 Concurrency config is parallel='none', perCoreThreadCount=true, 
 threadCount=2, useUnlimitedThreads=false  
  
 Running net.thornydev.mybatis.test.koan01.Koan01  
   

 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec   
   

 learnBasicConfigurationSetup(net.thornydev.mybatis.test.koan01.Koan01)  Time 
 elapsed: 0.1 secRunning net.thornydev.mybatis.test.koan02.Koan02  
 
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.113 sec
 learnToQueryViaXmlMapperReturningHashMap(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 1.072 
 seclearnToQueryMapperReturningHashMapWithParameterInput(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 0.005 
 seclearnToQueryViaXmlMapperReturningListOfHashMaps(net.thornydev.mybatis.test.koan02.Koan02)
   Time elapsed: 0.036 secRunning net.thornydev.mybatis.test.koan03.Koan03
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec
 learnToQueryViaXmlMapperReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.026 
 seclearnToQueryViaXmlMapperReturningCountryDomainObject(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.008 
 seclearnToQueryViaXmlMapperReturningListOfCountries(net.thornydev.mybatis.test.koan03.Koan03)
   Time elapsed: 0.033 secRunning net.thornydev.mybatis.test.koan04.Koan04
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
 learnToQueryViaXmlMapperReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.02 
 seclearnToQueryViaXmlMapperReturningCountryDomainObject(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.003 
 seclearnToQueryViaXmlMapperReturningListOfCountries(net.thornydev.mybatis.test.koan04.Koan04)
   Time elapsed: 0.017 secRunning net.thornydev.mybatis.test.koan05.Koan05
 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.052 sec
 learnToQueryViaMapperClassReturningCountryDomainObject(net.thornydev.mybatis.test.koan05.Koan05)
   Time elapsed: 0.011 
 seclearnToQueryViaMapperClassReturningListOfCountries(net.thornydev.mybatis.test.koan05.Koan05)
   Time elapsed: 0.014 
 seclearnToQueryViaMapperClassReturningHashMapOfCountriesKeyedById(net.thornydev.mybatis.test.koan05.Koan05)
   Time elapsed: 0.027 secRunning net.thornydev.mybatis.test.koan06.Koan06
 Tests run: 6, 

[jira] (MSITE-642) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.1:site: java.lang.ExceptionInInitializerError: null

2012-08-18 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSITE-642.
-

Resolution: Not A Bug

 An API incompatibility was encountered while executing 
 org.apache.maven.plugins:maven-site-plugin:3.1:site: 
 java.lang.ExceptionInInitializerError: null
 ---

 Key: MSITE-642
 URL: https://jira.codehaus.org/browse/MSITE-642
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
Affects Versions: 3.1
 Environment: Using Maven 3.0.4
Reporter: David Pilato
 Attachments: mavensite3.log, pom.xml, pom.xml


 After updating maven site version from 3.0 to 3.1, I get the following error 
 when running mvn clean site on my project.
 As far as I can see, the error come from : 
 Caused by: org.apache.commons.logging.LogConfigurationException: Invalid 
 class loader hierarchy.  You have more than one version of 
 'org.apache.commons.logging.Log' visible, which is not allowed.
   at 
 org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385)
   ... 61 more
 Full log is attached.
 I added my parent pom.xml file and the pom.xml file for the first module 
 (which fails).
 Hope this help.
 David.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

2012-08-18 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MSITE-639:
--

Affects Version/s: (was: 3.0-beta-3)
   3.0

 sub-project tries to fetch a site_en.xml even though no locales are configured
 --

 Key: MSITE-639
 URL: https://jira.codehaus.org/browse/MSITE-639
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
Affects Versions: 3.0
 Environment: Windows 7 64bit,  Sun JDK 1.6.0_27
Reporter: Martin Goldhahn
 Attachments: parent-project.zip, sub-project.zip


 I have a parent project that has a site descriptor and a pom project that has 
 the parent project as parent. Neither of them defines the locales parameter 
 of the site plugin.
 When I try to build the sub-project, I get an error that Maven cannot find 
 the site_en.xml descriptor of the parent project. Why doesn't it just use the 
 site.xml?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-628) Format of report goal names for /project/menu/item/@ref not properly documented

2012-08-18 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306491#comment-306491
 ] 

Dennis Lundberg commented on MSITE-628:
---

Hi Andreas,

I can't find the documentation for the attribute you are writing about at
http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html#class_item

What am I missing?

 Format of report goal names for /project/menu/item/@ref not properly 
 documented
 ---

 Key: MSITE-628
 URL: https://jira.codehaus.org/browse/MSITE-628
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Improvement
  Components: documentation
Affects Versions: 3.0
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Andreas Sewe
Priority: Minor

 This is probably just a documentation issue rather than a bug: I am unable 
 (using Maven 3.0.4, {{maven-site-plugin}} 3.0) to set 
 {{/project/menu/item/@ref}} such that the plugin actually recognizes the 
 reference:
 {quote}
 [WARNING] Unrecognised reference: 'project-info-reports:mailing-list'
 {quote}
 (Also, just {{mailing-list}} and 
 {{maven-project-info-reports-plugin:mailing-list}} won't work either.)
 The documentation in the XML Schema is unfortunately not very helpful:
 {quote}
 A reference to a pre-defined menu item, such as a report (specified by the 
 report goal name). Any elements explicitly given override those from the 
 pre-defined reference.
 {quote}
 An example showing the proper _report goal name_ format would thus be a 
 helpful addition to the XML Schema.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-862) excludedGroups property does not work with JUnit

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-862.
---

   Resolution: Fixed
Fix Version/s: 2.13.0
 Assignee: Kristian Rosenvold

Added checks for various conditions that can cause groups to go ignored in 
r1374642. Also added explicit IT for excludedgroups

 excludedGroups property does not work with JUnit
 

 Key: SUREFIRE-862
 URL: https://jira.codehaus.org/browse/SUREFIRE-862
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: Windows, Maven 3.0.3
Reporter: Rene Grohmann
Assignee: Kristian Rosenvold
 Fix For: 2.13.0


 If i use the groups property in my maven configuration everything works how 
 expected. The plugin only selects the tests with the specific category. On 
 the other Hand, if i use the excludedGroups property the plugin could not 
 find any tests to run.
 plugin
   artifactIdmaven-surefire-plugin/artifactId
   version2.11/version
   dependencies
 dependency
   groupIdorg.apache.maven.surefire/groupId
 artifactIdsurefire-junit47/artifactId
 version2.12/version
 /dependency
   /dependencies
   configuration 
 excludedGroupsde.test.junit.categories.IntegrationTest/excludedGroups
   /configuration
 /plugin

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-860) additionalClasspathElement doesn't work for folders with jar filers

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold updated SUREFIRE-860:


Issue Type: Improvement  (was: Bug)

 additionalClasspathElement doesn't work for folders with jar filers
 ---

 Key: SUREFIRE-860
 URL: https://jira.codehaus.org/browse/SUREFIRE-860
 Project: Maven Surefire
  Issue Type: Improvement
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: windows maven2 maven3
Reporter: necromantiarian

 used such config
 version2.12/version
 configuration
  additionalClasspathElements

 additionalClasspathElementC:/mycompany/lib/*.jar/additionalClasspathElement
  /additionalClasspathElements
 /configuration
 wanted to include a lot of *.jar files to classpath
 observed:
 surefire.test.class.path=D:\zf\workspace\test\target\test-classes;D:\zf\workspace\test\target\classes;C:\Users\myuser\.m2\repository\junit\junit\4.10\junit-4.10.jar;C:\Users\myuser\.m2\repository\org\hamcrest\hamcrest-core\1.1\hamcrest-core-1.1.jar;C:/mycompany/lib/*.jar
 and got ClassNotFoundException
 expected:
 the classes to be found and all the jars in classpath, just like maven libs
 note:
 tried also  
 additionalClasspathElementC:/mycompany/lib//additionalClasspathElement
 tried older versions of plugin too
 Am i doing smth wrong ?
 please advise

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-614) site plugin failure when forking a lifecycle

2012-08-18 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306493#comment-306493
 ] 

Dennis Lundberg commented on MSITE-614:
---

If I comment out org.apache.karaf.tooling:features-maven-plugin from 
test-assembly/pom.xml the build succeeds fine. My conclusion from that is that 
features-maven-plugin doesn't work correctly.

 site plugin failure when forking a lifecycle
 

 Key: MSITE-614
 URL: https://jira.codehaus.org/browse/MSITE-614
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Andreas Pieber
 Attachments: 5ebbfe13_maven-test.tar.gz


 If you execute mvn site in the attached test project it fails because of 
 the forked cycles. The test project could therefore not be resolved in the 
 maven plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-849) Properites groups and excludedGroups do not enable JUnit47 provider

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-849.
---

   Resolution: Fixed
Fix Version/s: 2.13.0
 Assignee: Kristian Rosenvold

Added failure conditions for some states that may cause groups to be silently 
ignored in r1374642. Also added ITs for all the cases mentioned inthis issue

 Properites groups and excludedGroups do not enable JUnit47 provider
 ---

 Key: SUREFIRE-849
 URL: https://jira.codehaus.org/browse/SUREFIRE-849
 Project: Maven Surefire
  Issue Type: Bug
  Components: Junit 4.x support
Affects Versions: 2.12
Reporter: Marcin Kuthan
Assignee: Kristian Rosenvold
 Fix For: 2.13.0


 I'm trying to define {{groups}} or {{excludeGroups}} for JUnit execution. 
 When I define property, JUnit4 provider is used, and the groups are ignored. 
 To enable group support I have to define {{parallel}} parameter or define 
 JUnit47 provider explicitly as plugin dependency.
 The plugin documentation is also inconsistent. The following goals 
 documentation defines, that JUnit47 provider will be enabled: 
 [http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#groups]
 [http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#excludedGroups]
 But on 
 [http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html], 
 the formula for provider selection define only {{parallel}} parameter. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-852) org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.NullPointerException: null

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-852.
---

Resolution: Cannot Reproduce
  Assignee: Kristian Rosenvold

The stacktrace in the bug report is not from 2.12, as the github repository 
seems to use. Additionally this code has been chaged fairly heavily and is no 
longer the same. Please reopen if you can reproduce on newer versions

 org.apache.maven.surefire.booter.SurefireExecutionException: null; nested 
 exception is java.lang.NullPointerException: null 
 

 Key: SUREFIRE-852
 URL: https://jira.codehaus.org/browse/SUREFIRE-852
 Project: Maven Surefire
  Issue Type: Bug
  Components: TestNG support
 Environment: MacOSX Lion - 10.7.3
 https://github.com/livetribe/livetribe-slp/tree/bug
Reporter: Alan Cabrera
Assignee: Kristian Rosenvold

 org.apache.maven.surefire.booter.SurefireExecutionException: null; nested 
 exception is java.lang.NullPointerException: null
 java.lang.NullPointerException
   at java.util.ArrayList.addAll(ArrayList.java:472)
   at 
 org.apache.maven.surefire.report.ReporterManager.testSetCompleted(ReporterManager.java:232)
   at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.finishTestSuite(TestNGDirectoryTestSuite.java:185)
   at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:159)
   at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
   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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
   at 
 org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
 [INFO] 
 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-861) Overriding excludes in profile does not achieve desired result

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold updated SUREFIRE-861:


Issue Type: Improvement  (was: Bug)

 Overriding excludes in profile does not achieve desired result
 --

 Key: SUREFIRE-861
 URL: https://jira.codehaus.org/browse/SUREFIRE-861
 Project: Maven Surefire
  Issue Type: Improvement
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: Win 7 Java 6 u 30 64bit Mvn 3.0.4
Reporter: Karsten Tinnefeld
Priority: Minor

 Overriding excludes in a profile does not work, the override is simply 
 ignored. This configuration should prevent surefire from running certain 
 tests except when the profile run-integration-tests is set:
 project ...
   build
   pluginManagement
   plugins
   plugin
   
 artifactIdmaven-surefire-plugin/artifactId
   version2.12/version
   configuration
   excludes
   
 exclude**/*IntegrationTest.java/exclude
   /excludes
   /configuration
   /plugin
   /plugins
   /pluginManagement
   /build
   profiles
   profile
   idrun-integration-tests/id
   build
   pluginManagement
   plugins
   plugin
   
 artifactIdmaven-surefire-plugin/artifactId
   configuration
   excludes /
   /configuration
   /plugin
   /plugins
   /pluginManagement
   /build
   /profile
   /profiles
 /project
 As a work-around, this ugly syntax can be applied:
 project ...
   profiles
   profile
   idrun-integration-tests/id
   build
   pluginManagement
   plugins
   plugin
   
 artifactIdmaven-surefire-plugin/artifactId
   configuration
   excludes
   
 excludeNONE/exclude
   /excludes
   /configuration
   /plugin
   /plugins
   /pluginManagement
   /build
   /profile
   /profiles
 /project
 However, I consider this a bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-905) Surefore report plugin only executed tests once.Junit Categorization is not possibel

2012-08-18 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated SUREFIRE-905:
-

Description: 
When I am trying to run categorized junit tests ,
maven surefire pluing run only first group. All other groups are skipped.
pom.xml
{code:xml}
   plugin
groupIdorg.apache.maven.plugins/groupId

artifactIdmaven-surefire-report-plugin/artifactId
version2.12.2/version
reportSets
reportSet
idunit/id
configuration
 
groupscom.mycompany.mavenproject2.UnitTest/groups 
reportsDirectory 
${project.build.directory}/surefire-reports/unit /reportsDirectory

outputNamesurefire-report-unit/outputName

reportNameSuffixUNIT/reportNameSuffix 
/configuration
reports
reportreport/report
/reports
/reportSet
reportSet
idcomp/id
configuration

groupscom.mycompany.mavenproject2.ComponentTest/groups 
reportsDirectory 
${project.build.directory}/surefire-reports/comp/reportsDirectory 

reportNameSuffixCOMPONENT/reportNameSuffix 

outputNamesurefire-report-comp/outputName 
/configuration 
reports
reportreport/report
/reports
/reportSet
reportSet
idsys/id
configuration

groupscom.mycompany.mavenproject2.SystemTest/groups
reportsDirectory 
${project.build.directory}/surefire-reports/sys/reportsDirectory

reportNameSuffixSYSTEM/reportNameSuffix 

outputNamesurefire-report-sys/outputName 
/configuration 
reports
reportreport/report
/reports
/reportSet
/reportSets
   
/plugin
{code}

With output
{noformat}
 T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, 
useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
UnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec

Results :

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0


[surefire:test]
Skipping execution of surefire because it has already been run for this 
configuration

[surefire:test]
Skipping execution of surefire because it has already been run for this 
configuration

[surefire:test]
Skipping execution of surefire because it has already been run for this 
configuration
{noformat}


  was:
When I am trying to run categorized junit tests ,
maven surefire pluing run only first group. All other groups are skipped.
pom.xml
   plugin
groupIdorg.apache.maven.plugins/groupId

artifactIdmaven-surefire-report-plugin/artifactId
version2.12.2/version
reportSets
reportSet
idunit/id
configuration
 
groupscom.mycompany.mavenproject2.UnitTest/groups 
reportsDirectory 
${project.build.directory}/surefire-reports/unit /reportsDirectory

outputNamesurefire-report-unit/outputName

reportNameSuffixUNIT/reportNameSuffix 
/configuration
reports
reportreport/report
/reports
/reportSet
reportSet
idcomp/id

[jira] (SUREFIRE-848) NPE in org.apache.maven.plugin.surefire.report.AbstractTextReporter

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-848.
---

   Resolution: Fixed
Fix Version/s: 2.13.0
 Assignee: Kristian Rosenvold

Fixed in the reporter refactoring in r1374259

 NPE in org.apache.maven.plugin.surefire.report.AbstractTextReporter
 ---

 Key: SUREFIRE-848
 URL: https://jira.codehaus.org/browse/SUREFIRE-848
 Project: Maven Surefire
  Issue Type: Bug
  Components: Junit 4.x support, Maven Surefire Plugin
Affects Versions: 2.12
Reporter: Stephan Schroevers
Assignee: Kristian Rosenvold
 Fix For: 2.13.0

 Attachments: example.tbz


 The combination Surefire/JUnit 4 causes a {{NullPointerException}} in 
 {{org.apache.maven.plugin.surefire.report.AbstractTextReporter}} if one has a 
  {{RunListener}} configured which (for whatever reason) throws an exception 
 in its {{#testRunStarted(Description)}} method.
 I have [attached|^example.tbz] a dummy project; run {{`mvn test`}} to see the 
 problem. The cause of this issue is that {{AbstractTextReporter}} initializes 
 its {{testResults}} field when 
 {{AbstractTextReporter#testSetStarting(ReportEntry)}} is called, which (it 
 seems) doesn't happen until JUnit invokes 
 {{RunNotifier#fireTestStarted(Description)}}. This is too late, because an 
 exception during the invocation of 
 {{RunNotifier#fireTestRunStarted(Description)}} causes 
 {{AbstractTextReporter#testError(ReportEntry, String, String)}} to be 
 invoked. The result is an NPE on line 103.
 Stacktrace:
 {noformat}
 Exception in thread ThreadedStreamConsumer java.lang.NullPointerException
   at 
 org.apache.maven.plugin.surefire.report.AbstractTextReporter.testError(AbstractTextReporter.java:103)
   at 
 org.apache.maven.plugin.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:87)
   at 
 org.apache.maven.plugin.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:150)
   at 
 org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:115)
   at 
 org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)
   at java.lang.Thread.run(Thread.java:619)
 {noformat}
 Note that this issue seems to have been the root cause of SUREFIRE-157; the 
 [last 
 comment|jira.codehaus.org/browse/SUREFIRE-157?focusedCommentId=197215#comment-197215]
  to that ticket also pointed to the late initialisation of the 
 {{testResults}} field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-824) SpecificTestClassFilterTest currently fails on windows

2012-08-18 Thread Kristian Rosenvold (JIRA)

 [ 
https://jira.codehaus.org/browse/SUREFIRE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-824.
---

   Resolution: Fixed
Fix Version/s: 2.13.0
 Assignee: Kristian Rosenvold

It now pass on windows

 SpecificTestClassFilterTest currently fails on windows
 --

 Key: SUREFIRE-824
 URL: https://jira.codehaus.org/browse/SUREFIRE-824
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.12
 Environment: Windows 7 64 bit, Java 6, maven 3.0.3
Reporter: Jan Sievers
Assignee: Kristian Rosenvold
 Fix For: 2.13.0

 Attachments: surefire-api-reports.zip, surefirebuild.log, 
 surefire-ITs-target.zip


 When building the current 2.13-SNAPSHOT version of surefire (commit 5d0b1b1 
 from http://github.com/apache/maven-surefire.git), the unit test
 SpecificTestClassFilterTest
 fails on windows. Seems like a file separator issue (filters with '/' used in 
 the test only work on filesystems with a '/' file separator).
 See build log and surefire logs attached.
 Not sure if related but ITs 
 Failed tests:   
 testSingleTestInOneExecutionOfMultiExecutionProject(org.apache.maven.surefire.its.jiras.Surefire806SpecifiedTestControlsIT):
  Reports directory is missing: 
 C:\git\github\maven-surefire\surefire-integration-tests\target\Surefire806SpecifiedTestControlsIT\surefire-806-specifiedTests-multi\target\surefire-reports
   
 testSingleTestInSingleExecutionProject(org.apache.maven.surefire.its.jiras.Surefire806SpecifiedTestControlsIT):
  Reports directory is missing: 
 C:\git\github\maven-surefire\surefire-integration-tests\target\Surefire806SpecifiedTestControlsIT\surefire-806-specifiedTests-single\target\surefire-reports
   
 testJUnitRunCategoryAB(org.apache.maven.surefire.its.jiras.Surefire809GroupExpressionsIT):
  Reports directory is missing: 
 C:\git\github\maven-surefire\surefire-integration-tests\target\Surefire809GroupExpressionsIT\surefire-809-groupExpr-junit48\target\surefire-reports
   
 testTestNGRunCategoryAB(org.apache.maven.surefire.its.jiras.Surefire809GroupExpressionsIT):
  Reports directory is missing: 
 C:\git\github\maven-surefire\surefire-integration-tests\target\Surefire809GroupExpressionsIT\surefire-809-groupExpr-testng\target\surefire-reports
 also fail for me.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-650) Problem with multiple executions of surefire within site plugin 3.0

2012-08-18 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306498#comment-306498
 ] 

Dennis Lundberg commented on MSITE-650:
---

I've had a look at the Surefire mojos. AbstractSurefireMojo has the checksum 
calculator in it, but AbstractSurefireReportMojo does not and it does not 
inherit from AbstractSurefireMojo either. Judging by that the behavior is 
correct, because the configuration is the same when you do not include the 
configuration of maven-surefire-report-plugin in the calculation.

 Problem with multiple executions of surefire within site plugin 3.0
 ---

 Key: MSITE-650
 URL: https://jira.codehaus.org/browse/MSITE-650
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Kristian Rosenvold

 There is a test project attached to SUREFIRE-905 that has a total of 4 
 executions of surefire, with different configuration for each.
 When running mvn clean install inside this project, surefire gets executed 
 4 times as expected. When running mvn site only the first execution gets 
 run, the last three get stopped by the configuration-checksum in surefire, 
 indicating they get executed with the *same* configuration as the default 
 execution.  (Surefire creates a SHA1 hash of all the mojo parameters to avoid 
 re-running the same configuration, which is why I conclude the three 
 executions get the same configuration as the default config)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1

2012-08-18 Thread Gary Clayburg (JIRA)

[ 
https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306500#comment-306500
 ] 

Gary Clayburg commented on MCHANGES-285:


I finally got back to looking at this issue.  This patch worked great for me.  
Thanks for the help, guys.

So what is the process for getting this patch committed and and released?

 SAXException parsing JIRA XML from JIRA 5.1 
 

 Key: MCHANGES-285
 URL: https://jira.codehaus.org/browse/MCHANGES-285
 Project: Maven 2.x Changes Plugin
  Issue Type: Bug
  Components: jira
Affects Versions: 2.7.1
 Environment: osx rhel sun java 1.6.0_30
Reporter: Micah Whitacre
 Attachments: patch-2.7.x.txt, patch.txt


 When trying to generate a changes report from a JIRA instance running 5.1[1] 
 I get the following exception 
 [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1
 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase 
 getResponseBody
 WARNING: Going to buffer response body of large or unknown size. Using 
 getResponseBodyAsStream instead is recommended.
 [INFO] Downloading from JIRA at: 
 http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none
 [WARNING] 
 org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
   at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
   at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
   at 
 org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
   at 
 org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
   at 
 org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
   at 
 org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
   at 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
   at 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
   at 
 org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
   at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
   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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 Caused by: org.xml.sax.SAXParseException: The entity name must immediately 
 follow the '' in the entity reference.
   at 
 org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
 Source)
   at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
   at