Problem when mvn site:site `Generating "Dependencies" report'
Locked
 
|
Hello,
I try use maven site plugin and it can generate project site well, but something wrong with dependencies report. there are some message : ============================================================= [INFO] Generating "Plugin Management" report. [INFO] Generating "Mailing Lists" report. [INFO] Generating "Continuous Integration" report. [INFO] Generating "Project License" report. [INFO] Generating "Project Team" report. [INFO] Generating "Source Repository" report. [INFO] Generating "Issue Tracking" report. [INFO] Generating "Project Summary" report. [INFO] Generating "Project Plugins" report. [INFO] Generating "Dependencies" report. [WARNING] Unable to process class com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File C:\Documents and Settings\qty\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 60 at org.apache.bcel.classfile.Constant.readConstant(Constant.java:146) at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:67) at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222) at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136) at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92) at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:285) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1278) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:423) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:268) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ============================================================= some JARs are unanalyzed. I try use mvn dpenedency:tree to see any problem with dependencies and everything is ok. Someone can tell me how to exclude JARs in dependencies report. Thank a lot. |
Re: Problem when mvn site:site `Generating "Dependencies" report'
|
Check that the file is not corrupted: use the sha1 or md5 from the central
repo to check the one you downloaded matches. You can delete the local file if it was download and have a look if there's a warning when downloading it. Cheers. 2008/10/6 qrtt1 <[hidden email]> > > Hello, > > I try use maven site plugin and it can generate project site well, but > something wrong with dependencies report. there are some message : > > ============================================================= > [INFO] Generating "Plugin Management" report. > [INFO] Generating "Mailing Lists" report. > [INFO] Generating "Continuous Integration" report. > [INFO] Generating "Project License" report. > [INFO] Generating "Project Team" report. > [INFO] Generating "Source Repository" report. > [INFO] Generating "Issue Tracking" report. > [INFO] Generating "Project Summary" report. > [INFO] Generating "Project Plugins" report. > [INFO] Generating "Dependencies" report. > [WARNING] Unable to process class > com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File > C:\Documents and > Settings\qty\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar > org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in > constant > pool: 60 > at > org.apache.bcel.classfile.Constant.readConstant(Constant.java:146) > at > org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:67) > at > > org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222) > at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136) > at > > org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92) > at > > org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:285) > at > > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1278) > at > > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:423) > at > > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:268) > at > > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > > org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) > at > > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) > at > > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > ============================================================= > > > some JARs are unanalyzed. I try use mvn dpenedency:tree to see any problem > with dependencies and everything is ok. Someone can tell me how to exclude > JARs in dependencies report. > > Thank a lot. > -- > View this message in context: > http://www.nabble.com/Problem-when-mvn-site%3Asite-%60Generating-%22Dependencies%22-report%27-tp19831145p19831145.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! |
|
In reply to this post by qrtt1
On Sun, Oct 5, 2008 at 7:19 PM, qrtt1 <[hidden email]> wrote:
> > [WARNING] Unable to process class > com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File > C:\Documents and > Settings\qty\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar > org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant > pool: 60 It appears this class/jar is the source of your problems. Perhaps IBM has a newer version of icu4j? Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
|
As I suspected, there are several newer versions (3.4.4, 3.6.1, 3.8):
http://repo1.maven.org/maven2/com/ibm/icu/icu4j/ Try the latest v3.8 instead. Wayne On Sun, Oct 5, 2008 at 11:44 PM, Wayne Fay <[hidden email]> wrote: > It appears this class/jar is the source of your problems. Perhaps IBM > has a newer version of icu4j? > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
|
Hi Wayne,
Thanks for your suggestion. but it's not a direct dependency. jaxen use xom and xom use icu4j. Maybe just ignore the warnings and errors.
|
Re: Problem when mvn site:site `Generating "Dependencies" report'
|
In reply to this post by qrtt1
see http://jira.codehaus.org/browse/MPIR-142
-Lukas qrtt1 wrote: > Hello, > > I try use maven site plugin and it can generate project site well, but > something wrong with dependencies report. there are some message : > > ============================================================= > [INFO] Generating "Plugin Management" report. > [INFO] Generating "Mailing Lists" report. > [INFO] Generating "Continuous Integration" report. > [INFO] Generating "Project License" report. > [INFO] Generating "Project Team" report. > [INFO] Generating "Source Repository" report. > [INFO] Generating "Issue Tracking" report. > [INFO] Generating "Project Summary" report. > [INFO] Generating "Project Plugins" report. > [INFO] Generating "Dependencies" report. > [WARNING] Unable to process class > com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File > C:\Documents and > Settings\qty\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar > org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant > pool: 60 > at org.apache.bcel.classfile.Constant.readConstant(Constant.java:146) > at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:67) > at > org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222) > at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136) > at > org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92) > at > org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:285) > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1278) > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:423) > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:268) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > ============================================================= > > > some JARs are unanalyzed. I try use mvn dpenedency:tree to see any problem > with dependencies and everything is ok. Someone can tell me how to exclude > JARs in dependencies report. > > Thank a lot. --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
If anyone has a resolution for this issue please let us know... I'm watching the Jira ticket too but any workaround in the meantime would be great.
Thanks. --Kevin
|
|
|
In reply to this post by qrtt1
The fact that it is not a direct dependency does not really matter in
this particular case. You have a bad jar in your (transitive) deps, like it or not. I would simply add a dependency on a newer version of this jar in your own project eg [3.8]. I would also encourage the "xom" people to produce a new version that depends on a build of icu4j that is not broken. And then encourage the "jaxen" people to upgrade to that xom version. Wayne On Mon, Oct 6, 2008 at 1:42 AM, qrtt1 <[hidden email]> wrote: > > Hi Wayne, > > Thanks for your suggestion. > > but it's not a direct dependency. > > jaxen use xom and xom use icu4j. > > Maybe just ignore the warnings and errors. > > > Wayne Fay wrote: >> >> As I suspected, there are several newer versions (3.4.4, 3.6.1, 3.8): >> http://repo1.maven.org/maven2/com/ibm/icu/icu4j/ >> >> Try the latest v3.8 instead. >> >> Wayne >> >> On Sun, Oct 5, 2008 at 11:44 PM, Wayne Fay <[hidden email]> wrote: >>> It appears this class/jar is the source of your problems. Perhaps IBM >>> has a newer version of icu4j? >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [hidden email] >> For additional commands, e-mail: [hidden email] >> >> >> > > -- > View this message in context: http://www.nabble.com/Problem-when-mvn-site%3Asite-%60Generating-%22Dependencies%22-report%27-tp19831145p19834001.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
«
Return to Maven - Users
|
1 view|%1 views
Loading...
| Free forum by Nabble | Edit this page |