You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nigel Magnay (JIRA)" <ji...@codehaus.org> on 2006/03/28 23:25:44 UTC
[jira] Commented: (MSITE-85) Dependency report broken if M1
artifacts referenced
[ http://jira.codehaus.org/browse/MSITE-85?page=comments#action_62193 ]
Nigel Magnay commented on MSITE-85:
-----------------------------------
Ok - but - the workflow doesn't allow re-opening of the duplicate source (if that is MIPIR-19).
Reading it seems to indicate closed due to non-reproducability, not due to it being fixed (e.g. there is nothing in the SVN tab) - if it is, that's great, but it's not easy to tell!
> Dependency report broken if M1 artifacts referenced
> ---------------------------------------------------
>
> Key: MSITE-85
> URL: http://jira.codehaus.org/browse/MSITE-85
> Project: Maven 2.x Site Plugin
> Type: Bug
> Reporter: Nigel Magnay
> Assignee: Brett Porter
>
>
> Workaround is :
> <excludeDefaults>true</excludeDefaults> in reporting to disable the default project-info reports.
> Otherwise you get
> [INFO] Generate "Dependencies" report.
> [INFO] ----------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Can't find a valid Maven project in the repository for the artifact [kernel:framework:1.0(8)].
> [INFO] ----------------------------------------------------------------------------
> [INFO] Trace
--
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