You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@codehaus.org> on 2011/12/28 12:25:02 UTC
[jira] (MPIR-238) Dependency File Details section of the
dependencies report shows 'target/classes' for reactor artifacts.
Christian Schulte created MPIR-238:
--------------------------------------
Summary: Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
Key: MPIR-238
URL: https://jira.codehaus.org/browse/MPIR-238
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependency-info
Affects Versions: 2.4
Reporter: Christian Schulte
Priority: Minor
Generating the dependencies report in a multi-module project leads to incorrect entries in the 'Dependency File Details' section of the dependencies report. For example, the [Maven Release Plugin Dependency File Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details] report contains the following entry:
||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
|maven-release-manager/target/classes|-|0|0|0|-|release|
Building the site of a single module ('mvn site' in that modules directory), the correct entries are shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-238) Dependency File Details section of the
dependencies report shows 'target/classes' for reactor artifacts.
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287016#comment-287016 ]
Christian Schulte commented on MPIR-238:
----------------------------------------
This also affects the 'Dependency Repository Locations' report, which does not link to snapshot repositories in such situations.
> Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
> --------------------------------------------------------------------------------------------------------
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
> Affects Versions: 2.4
> Reporter: Christian Schulte
> Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to incorrect entries in the 'Dependency File Details' section of the dependencies report. For example, the [Maven Release Plugin Dependency File Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details] report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory), the correct entries are shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-238) Dependency File Details section of the
dependencies report shows 'target/classes' for reactor artifacts.
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287015#comment-287015 ]
Christian Schulte edited comment on MPIR-238 at 12/28/11 2:50 PM:
------------------------------------------------------------------
The cause is class 'org.apache.maven.ReactorReader' falling back to returning directories when the 'compile' phase has completed which is the case for various report plugins marked '@execute phase="generate-test-sources"'. MPIR-238.patch contains a patch for the dependencies report adding '@execute phase="package"' to make the reactor reader stop returning directories. MPIR-238-ReactorReader.patch contains a patch for that class to not resolve to directories when not executing the default lifecycle.
was (Author: schulte2005):
The cause is class 'org.apache.maven.ReactorReader' falling back to returning directories when the 'compile' phase has completed which is the case for various report plugins marked '@execute phase="generate-sources"'. MPIR-238.patch contains a patch for the dependencies report adding '@execute phase="package"' to make the reactor reader stop returning directories. MPIR-238-ReactorReader.patch contains a patch for that class to not resolve to directories when not executing the default lifecycle.
> Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
> --------------------------------------------------------------------------------------------------------
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
> Affects Versions: 2.4
> Reporter: Christian Schulte
> Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to incorrect entries in the 'Dependency File Details' section of the dependencies report. For example, the [Maven Release Plugin Dependency File Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details] report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory), the correct entries are shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-238) Dependency File Details section of the
dependencies report shows 'target/classes' for reactor artifacts.
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schulte updated MPIR-238:
-----------------------------------
Attachment: MPIR-238-ReactorReader.patch
Updated patch to test for the 'pre-clean' phase instead of 'clean'.
> Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
> --------------------------------------------------------------------------------------------------------
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
> Affects Versions: 2.4
> Reporter: Christian Schulte
> Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch, MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to incorrect entries in the 'Dependency File Details' section of the dependencies report. For example, the [Maven Release Plugin Dependency File Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details] report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory), the correct entries are shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-238) Dependency File Details section of the
dependencies report shows 'target/classes' for reactor artifacts.
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schulte updated MPIR-238:
-----------------------------------
Attachment: MPIR-238-ReactorReader.patch
MPIR-238.patch
The cause is class 'org.apache.maven.ReactorReader' falling back to returning directories when the 'compile' phase has completed which is the case for various report plugins marked '@execute phase="generate-sources"'. MPIR-238.patch contains a patch for the dependencies report adding '@execute phase="package"' to make the reactor reader stop returning directories. MPIR-238-ReactorReader.patch contains a patch for that class to not resolve to directories when not executing the default lifecycle.
> Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
> --------------------------------------------------------------------------------------------------------
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
> Affects Versions: 2.4
> Reporter: Christian Schulte
> Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to incorrect entries in the 'Dependency File Details' section of the dependencies report. For example, the [Maven Release Plugin Dependency File Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details] report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory), the correct entries are shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira