[
http://jira.codehaus.org/browse/MOJO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Vicente reassigned MOJO-1164:
-----------------------------------
Assignee: David Vicente
> Detailed dashboard report has broken links when poms have non-hierarchical
> parents
> ----------------------------------------------------------------------------------
>
> Key: MOJO-1164
> URL: http://jira.codehaus.org/browse/MOJO-1164
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
> Reporter: Stuart McCulloch
> Assignee: David Vicente
> Attachments: dashboard-broken-link-testcase.zip,
> DASHBOARD_PARENT_PROJECT.patch
>
>
> When using the dashboard plugin in a multi-module project, the site-deployed
> detailed dashboard report has broken links for the following cases:
> 1) a sub-module project defines a parent that is not the same as the
> containing project, for example:
> A
> |- B - C where C's parent is D, not B
> |- D
> 2) a sub-module project has an artifactId that is different to it's
> containing directory, for example:
> a/b/c/pom.xml where the artifactId in the pom is not 'c'
> this is because the site plugin uses the parent and the project artifactId to
> create the directory structure, whereas the dashboard plugin uses the module
> layout.
> Both of these cases are uncommon, but not improbable - and looking at the
> dashboard code this may be hard to fix, so this could be documented as a
> limitation.
> I've attached a testcase that recreates both cases - just use "mvn
> site-deploy" and it should write the reports to
> ${env.TEMP}/examples/dashboard/website
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
