If I turn off dependencyDetailsEnabled in the reporting section:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.1</version>
<configuration>
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
</configuration>
</plugin>
I have no issues. Since this flag determines if the plugin counts the
number of classes and or packages, I'm thinking this is using bcel and
bcel must have a problem. I see that some plugins are using 5.2 but if
I turn on -X -e, I can see that the dependency plugin is using 1.2.0.
Can someone update this dependency?
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2008 7:15 AM
To: Maven Users List
Subject: RE: Dependency report fails
Can the dependency report be configured to skip a series of depenencies?
If it can, I don't see a way...
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 4:35 PM
To: users@maven.apache.org
Subject: Dependency report fails
http://jira.codehaus.org/browse/MPIR-142
Any movement on this particular bug at all (or suggested workaround)?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
