You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2007/07/08 02:36:13 UTC
[jira] Commented: (MCHANGES-73) No longer integrates with JIRA
[ http://jira.codehaus.org/browse/MCHANGES-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101610 ]
Dennis Lundberg commented on MCHANGES-73:
-----------------------------------------
This seems strange. The 2.0-beta-2 release uses commons-httpclient:commons-httpclient:3.0.1, which in turn has a dependency on commons-codec:1.2. So unless you are using some sort of repository proxy there should be no problem for you. If you *are* using a proxy, make sure that you have commons-codec:commons-codec:1.2 in there.
> No longer integrates with JIRA
> ------------------------------
>
> Key: MCHANGES-73
> URL: http://jira.codehaus.org/browse/MCHANGES-73
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0-beta-2
> Environment: Windows XP, Linux (RHEL3)
> Reporter: Immo Huneke
>
> As of this morning (2nd April 2007), the Maven Changes Plugin suddenly stopped working with a fatal error. Nothing about our POMs or the JIRA system used here had changed overnight - yet we were seeing decoding errors in some builds. In an attempt to resolve the situation, we deleted the local Maven repository - with the result that now ALL builds failed during site generation! The configured issue-tracking section of the POM is as follows:
> <issueManagement>
> <system>JIRA</system>
> <url>http://jira-xtools.ldn.swissbank.com:7500/jira/secure/BrowseProject.jspa?pid=10193</url>
> </issueManagement>
> We previously had IssueNavigator.jspa, but the result was identical.
> Part of the error message is shown below:
> artifact org.apache.maven.skins:maven-default-skin: checking for updates from central
> Generating /sbclocal/icc/teamcity/buildagent1/ICC_Tools_BuildSystemHooks/SubversionHooks/target/site/jira-report.html
> Generate "Jira Report" report.
> JIRA lives at: http://jira-xtools.ldn.swissbank.com:7500/jira
> ------------------------------------------------------------------------
> FATAL ERROR
> ------------------------------------------------------------------------
> org/apache/commons/codec/DecoderException
> ------------------------------------------------------------------------
> Trace
> java.lang.NoClassDefFoundError: org/apache/commons/codec/DecoderException
> at org.apache.commons.httpclient.HttpMethodBase.<init>(HttpMethodBase.java:217)
> at org.apache.commons.httpclient.methods.GetMethod.<init>(GetMethod.java:88)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.download(AbstractJiraDownloader.java:479)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:241)
> at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:181)
> at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira