Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3.1
-
Fix Version/s: 2.4
-
Component/s: dependencies
-
Labels:None
-
Environment:HideApache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100)
Java version: 1.6.0_20
Java home: D:\Julien\jdk1.6.0_20\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"ShowApache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) Java version: 1.6.0_20 Java home: D:\Julien\jdk1.6.0_20\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
-
Number of attachments :
Description
Running mvn clean site on my project produce the following error:
[ERROR] IOException: D:\Projects\jwebunit\jwebunit-commons-tests\target\classes (Acces denied)
java.io.FileNotFoundException: D:\Projects\jwebunit\jwebunit-commons-tests\target\classes (Acces denied)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at java.util.jar.JarFile.<init>(JarFile.java:99)
at org.apache.maven.shared.jar.JarAnalyzer.<init>(JarAnalyzer.java:105)
at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:273)
at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1374)
at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:544)
at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:271)
It doesn't prevent the build to complete.
You can reproduce on the project:
https://jwebunit.svn.sourceforge.net/svnroot/jwebunit/trunk
Build instructions (need toolchains):
http://jwebunit.sourceforge.net/building-maven.html#Installing_Maven
Running mvn clean project-info-reports:dependencies works fine so I guess there is a bad interaction with another report.
What exactly is the bug? Is there something missing in the report? This is just an exception that is caught and logged in error mode but I see no bug here.