Am 16.12.2014 um 17:33 schrieb Gary Gregory: > The JIRA report is not generated with 'mvn clean site' because: > > [INFO] Generating "JIRA Report" report --- > maven-changes-plugin:2.4:jira-report > Dec 16, 2014 11:01:05 AM 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://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310467&statusIds=5&statusIds=6&resolutionIds=1&type=1&type=2&type=3&type=4&type=5&type=6&sorter/field=issuekey&sorter/order=DESC&sorter > /field=issuetype&sorter/order=ASC&sorter/field=fixVersions&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] > org.xml.sax.SAXParseException; systemId: > file:/C:/temp/rc/commons-configuration2-2.0-alpha2-src/target/jira-results.xml; > lineNumber: 104; columnNumber: 3; The element type "meta" must be > terminated by the matching end-tag "</meta>". > 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 org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown > Source) > at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:108) > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:98) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:709) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:319) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:135) > at > org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129) > at > org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182) > at > org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:141) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > 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:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > [INFO] The JIRA version is 'null' > [INFO] Generating "JavaDocs" report --- > maven-javadoc-plugin:2.10.1:javadoc > [INFO] > > An old maven-changes-plugin is in use here, maybe that has something to do > with it. > > Running with: > > Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; > 2014-08-11T16:58:10-04:00) > Maven home: C:\Java\apache-maven-3.2.3 > Java version: 1.7.0_71, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_71\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > > Gary
Good catch. Updating to version 2.11 of the maven-changes-plugin seems to fix the problem. But this is surely not a blocker for the release? Oliver > > On Fri, Dec 12, 2014 at 3:38 PM, Oliver Heger <oliver.he...@oliver-heger.de> > wrote: >> >> Hi all, >> >> this is a vote for the second alpha version of [configuration] 2.0 based >> on the first release candidate. After the first alpha version, a couple >> of enhancement requests have been implemented causing some minor changes >> on interfaces. Details are available in the release notes. >> >> The same disclaimer applies as for the first alpha release: >> - This release is according to the "release often and early" mantra. It >> is not yet perfect (e.g. there are lots of checkstyle errors, and it is >> expected that there are still some API changes). The purpose is to get >> feedback from the community regarding the new concepts implemented in >> this version. I hope, I have made this clear in the release notes. >> - In the past we decided that alpha releases should not go to Maven >> central. Therefore, I did not deploy the artifacts to Nexus; only the >> distributions were created. >> >> Configuration 2.0-alpha2 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/configuration >> (revision 7395) >> >> Details of changes since 1.10 and the first alpha version are in the >> release notes: >> >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt >> >> >> http://people.apache.org/~oheger/configuration-2.0-alpha2-rc1/changes-report.html >> >> Here is the tag: >> >> >> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_alpha2_RC1 >> (revision 1644517) >> >> Site: >> http://people.apache.org/~oheger/configuration-2.0-alpha2-rc1/ >> (note some links in the menu for version 1.10 are not yet working) >> >> KEYS: >> http://www.apache.org/dist/commons/KEYS >> >> Please review the release candidate and vote. >> This vote will close no sooner than 72 hours from now, i.e. after 2000 >> GMT 15-December 2014 >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but really should fix... >> [ ] -1 I oppose this release because... >> >> Thanks! >> Oliver >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org