[jira] Updated: (MOJO-1204) In Maven 1 style dashboard reports: summarize the report data per module

     [
http://jira.codehaus.org/browse/MOJO-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Vicente updated MOJO-1204:
--------------------------------

    Attachment: multi_module_project.png
                single_module_project.png

See these screenshoots.

does this suit your needs?

> In Maven 1 style dashboard reports: summarize the report data per module
> ------------------------------------------------------------------------
>
>                 Key: MOJO-1204
>                 URL: http://jira.codehaus.org/browse/MOJO-1204
>             Project: Mojo
>          Issue Type: Improvement
>          Components: dashboard
>         Environment: any
>            Reporter: Michael
>            Assignee: David Vicente
>         Attachments: multi_module_project.png, patch.txt, single_module_project.png
>
>
> The attached patch
> 1) prints "N/A" in cells when no report data is available

https://dav.codehaus.org/.... from behind a http proxy?

https://dav.codehaus.org/.... from behind a http proxy?

https://dav.codehaus.org/.... from behind a http proxy?

Stephen Connolly wrote:

> WAGON_VERSION: 1.0-beta-2
>
> I thought that we have moved to 1.0-beta-4?

AFAIK, one can still override the Wagon version bundled with the core
which the Mojo Parent does.

> Or is there some way I can force the use of 1.0-beta-4

Try using an <extension> in your POM.

Benjamin

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

https://dav.codehaus.org/.... from behind a http proxy?

https://dav.codehaus.org/.... from behind a http proxy?

Re: aspectJ plugin claims to compile on java 1.4 but require java5 runtime

david <at> davidkarlsen.com wrote:
> On Thu, 21 Aug 2008, nicolas de loof wrote:
> 
>> This is not realted to aspectJ 1.6.1 upgrade : the plugin code itself is
>> based on some java5 API classes and methods :
>>
>> new PrintWriter( File )
>> path.replace( String, String )
>> Element.getTextContent()
>> Document.normalizeDocument()
>>
>> I'm +1 for Java5 requirement.
> 
> Yeah - I forked the compiler and noticed the same methodcalls.
> PrintWriter can easly be replaced with new FileOutputStream( file f )
> path.replace can be replaced with StringUtils from commons-lang
> Element/Document stuff can be fixed by using other methods or adding a 
> DOM3 level parser.
> 
> What do we prefer? Probably this isn't a very huge problem since nobody 
> have reported it earlier (and I have not seen anybody complain on the 
> mailinglists either) - and maven 2.1 is moving in 1.5 direction anyways 
> AFAIK.
> 
> Should we call a vote - or just go for it?

Lots of users are still on 1.4 so the plugin should definitely stay 
there unless you are sure no-one use 1.5 anymore. There really isn't a 
whole lot to gain from moving to 1.5 other than less warnings about 
unchecked collection use[1]. So, please stay on 1.4 unless there are no 
users on 1.4.

[1]: which in itself is annoying but not worth requiring the entire user 
base to move to 1.5.

--
Trygve

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] Updated: (MOJO-1204) In Maven 1 style dashboard reports: summarize the report data per module

     [
http://jira.codehaus.org/browse/MOJO-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael updated MOJO-1204:
--------------------------

    Attachment: multi-module_patch.png

Maven 1 style dashboard with summary lines (as created with the attached patch).

> In Maven 1 style dashboard reports: summarize the report data per module
> ------------------------------------------------------------------------
>
>                 Key: MOJO-1204
>                 URL: http://jira.codehaus.org/browse/MOJO-1204
>             Project: Mojo
>          Issue Type: Improvement
>          Components: dashboard
>         Environment: any
>            Reporter: Michael
>            Assignee: David Vicente
>         Attachments: multi-module_patch.png, multi_module_project.png, patch.txt, single_module_project.png
>
>
> The attached patch
> 1) prints "N/A" in cells when no report data is available
> 2) prints a "Total for $component" summary line for each component in multi module builds
> 3) does not print any "Total" summary line for single module builds
>    (it seems unnecessary to me why you should summarize a single line - that is just duplication of information)

--

-- 
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

[jira] Commented: (MOJO-1204) In Maven 1 style dashboard reports: summarize the report data per module

    [
http://jira.codehaus.org/browse/MOJO-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146607#action_146607
] 

Michael commented on MOJO-1204:
-------------------------------

David:

thanks for your work. This greatly improves the report.

I have attached the screenshot "multi-module_patch.png" which shows how the report looks like with the
patch I attached. We build a multi module build "components" which includes three modules (runtime,
admin and another one), where runtime has another sub-module "extensions".

You may notice that the summary lines are in different color than the report lines.

I think it would be an improvement in your modifications if you would change the background color of the
summary line, as it is otherwise not possible to distinguish between data and summary rows if you scroll to
the right or have a quick look at the report: it is rather clumsy to figure out what entry is a sum (and hence
doesn't "count") and what is real data.

Have you included the "N/A" patch in your modifications? I just ask because this is not clear in the
screenshot you attached.

> In Maven 1 style dashboard reports: summarize the report data per module
> ------------------------------------------------------------------------
>
>                 Key: MOJO-1204
>                 URL: http://jira.codehaus.org/browse/MOJO-1204
>             Project: Mojo
>          Issue Type: Improvement
>          Components: dashboard
>         Environment: any
>            Reporter: Michael
>            Assignee: David Vicente
>         Attachments: multi-module_patch.png, multi_module_project.png, patch.txt, single_module_project.png
>
>
> The attached patch
> 1) prints "N/A" in cells when no report data is available
> 2) prints a "Total for $component" summary line for each component in multi module builds
> 3) does not print any "Total" summary line for single module builds
>    (it seems unnecessary to me why you should summarize a single line - that is just duplication of information)

--

-- 
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

Simian Plugin Enhancement

Hi,

There is a reporting plugin called simian-report-maven-plugin in the
sandbox. I've hacked this into an updated simian plugin, primarily to
add support for XML output. Basically this updated plugin has two
goals, 'simian' which outputs an XML report, and 'report' which
outputs both an XML report and an HTML report. The html report one is
designed to be run as a report, but the XML one can be run not as a
report, for example to check and possibly fail a build, or simply to
create the XML report for further downstream processing. This is very
similar to the way in which PMD, findbugs or checkstyle plugins can be
used. Its a bit more than a patch to the original plugin, as I've
considerably refactored things to ensure that common code is shared
between the reporting HTML and XML mojos.

My motiviations for doing this are:

I want an XML report to extract data from to add a new column to the
Xebia dashboard plugin.
I want an XML report for Hudson to extract data from.
CPD is ok, but Simian is better and is configurable.

I want to rename the simian-report-maven-plugin to
simian-maven-plugin, because it is now not just for reporting. Is
there any interest in adding this plugin to the codehaus mojo
collection? Please let me know if there is, and I will gladly
contribute my efforts. If there is not, I intend to publish it
independently, with respect to Miguel Griffa, its original author, and
following the Gnu LGPL terms under which it was made available.

Thanks for your interest.

Rupert Smith

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email