creadur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manuel Suárez Sánchez <>
Subject Re: [GSOC] Rat: Past, Present and Future
Date Sun, 08 Sep 2013 19:00:17 GMT
Hi Everyone.

Two months ago more less this topic was created at that time I was new in
the project and I didn´t know a lot of things about it but with the past of
time I was working in the project and I was learning more about it.

My objective is try to do this task: , I think that I made a lot
of changes, improvements and punish bad code in the project. My fork of the
project is here: . This is
open source project I would like that community review it and I would like
to receive a FeedBack(I know that I´m new in this world so I can do good
and bad things for me the most important is learning about the mistakes).
                 Before:    After:
Coverage       75%      96%
[image: Imágenes integradas 1]
Changes of Refactor:

-Deleted not used Vars, Class, Method.
-Change bad used of Java.
-Improved performance.
-Add Test class, Test Methods
-Apply PMD Changes.
-Format Code.
-Add JavaDoc.

I have still Two weeks to work in the project in the Timeline of GSOC, In
this time I would like to improve the project for this reason I would like
to work in one task( I need that all the community together try to find the
weakness point of the project), all this time I was working alone because I
thought that I don´t have time to finish it but I understand that it is
open source  and we need to work together. The community was made growing
up this project and it´s the great of Open Source Project.


2013/7/11 Robert Burrell Donkin <>

> On 07/10/13 23:49, Manuel Suárez Sánchez wrote:
>>> 1. scan the source, building a strongly-typed, immutable domain model
>> This point is basic to improve the project because now there aren´t a good
>> domain model and it´s very confused.
> I think that the question comes down to granularity.
> Here's one way that the two contrasting approach might work...
> With the full model approach, the source would be scanned completed into a
> model before the document contents were analysed. Once the analysis was
> complete, then the reporting would start. The process flow would be
> course-grained. This would cut across the grain of the current Rat design.
> With a message oriented architecture, the scanner would send each document
> to enrichment as soon as it was created. The enricher would take a look at
> the contents and add document-level meta-data, then pass on the enriched
> object as soon as it was created. Aggregate analysers would then build up
> the report. This would be sympathetic to the current Rat design.
> Retaining a streaming/messaging architecture means modelling at the
> message level (rather than more complete structures)
> <snip>
>  However, I think that the current streaming design isn't particularly
>>> intuitive or obvious. I would be happy to retain an improved streaming
>>> design.
>> I think that apache rat is a release audit tool, focused on licenses. In
>> the project you analyse a file(audio) and you get the license of the
>> file. Why
>> do you try to use streaming/message driven architecture?
> Performance at small memory footprint
> Robert

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message