I have been trying to get a build of 2.5.0-beta2 done over the past few
days but I have run into a few problems.  I am following the steps defined
on the release process page [1].  I am running into problems running mvn
release:prepare -DdryRun=true -Papache-release.  The first thing I ran into
was missing license headers and outdated RAT exclusions.  I was able to
work through those easily enough.  Now I am running into errors when maven
is running php unit tests.

[INFO]     [mkdir] Created dir:
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/surefire-reports
[INFO]     [mkdir] Created dir:
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/site/coverage-report
[INFO]     [mkdir] Created dir:
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/tmp
[INFO]      [exec] PHPUnit 3.6.11 by Sebastian Bergmann.
[INFO]      [exec]
[INFO]      [exec] The Xdebug extension is not loaded. No code coverage
will be generated.
[INFO]      [exec]
[INFO]      [exec]
[INFO]      [exec] PHP Fatal error:  Call to undefined function
apache\shindig\common\sample\mcrypt_module_open() in
/Users/rbaxter/workspaces/shindig/250_beta_2/php/src/apache/shindig/common/sample/Crypto.php
on line 66
[INFO]      [exec] ...............................SSSSSS
[INFO]      [exec] Result: 255
[INFO]      [xslt] Processing
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/surefire-reports/phpunit-testresults.xml
to /Users/rbaxter/workspaces/shindig/250_beta_2/php/target/surefire-reports/
xslt.info
[INFO]      [xslt] Loading stylesheet
/Users/rbaxter/workspaces/shindig/250_beta_2/php/test/config/phpunit_to_surefire.xslt
[INFO]      [xslt]
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/surefire-reports/phpunit-testresults.xml:1:1:
Fatal Error! Error reported by XML parser Cause:
org.xml.sax.SAXParseException: Premature end of file.
[INFO]      [xslt] Failed to process
/Users/rbaxter/workspaces/shindig/250_beta_2/php/target/surefire-reports/phpunit-testresults.xml


Since many of these problems should have been caught in previous betas I
feel like either I am not doing something right or we have not been
following the complete release process in the past.  We released the PHP
version for 2.5.0 beta1, were these unit tests not run?  I don't think
anyone has been actively working on the PHP version so I don't think this
is caused by a code change. Henry or Paul could you comment?

-Ryan

[1] http://shindig.apache.org/community/releasing.html

Reply via email to