macker-user — Questions, request for help, and feature discussions

Re: [macker-user] A query about compilation report and JUnit

[Paul C. <can...@po...>]

Yogesh --

By (1) I presume you are asking whether you can format javac's output=20
as HTML using Macker?  That you can't -- Macker operates on compiled=20
class files, and compilation is entirely outside its scope.

On (2), Macker can't do that now, though it's possible that the rules=20
in future versions might allow it.  For now, I recommend you look at a=20=

test coverage tool such as Clover, which gives more useful information=20=

anyway.

Cheers,

Paul


On Jan 8, 2004, at 5:12 AM, Yogesh Pandit wrote:

> Hi,
> =A0
> 1) Can we generate aCOMPILATION REPORT in HTML format using Macker ?
> =A0
> 2) Can Macker be used to check whether every public method in a Java=20=

> class has a corresponding JUnit test case ?
> =A0
> Thanking in advance.
> =A0
> Regards,
> Yogesh

[macker-user] A query about compilation report and JUnit

[Yogesh P. <iam...@ya...>]

Hi,
 
1) Can we generate a COMPILATION REPORT in HTML format using Macker ? 
 
2) Can Macker be used to check whether every public method in a Java class has a corresponding JUnit test case ?
 
Thanking in advance.
 
Regards,
Yogesh


---------------------------------
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes

[macker-user] legacy code problem

[Michael D. <Mi...@Di...>]

Hi,

I am new to this group, so please bare with me and my questions if  by some
occasion this question/s have been already asked.

Now to the point, we are in the midst of the architectural changes in the
existing code. I decided to enforce new architecture with Macker, but I
don't want the old code to pop up as problem (we will deal with it offline);
I only want to monitor that new code is aligned with guidelines. what I need
is some kind of "suppress" feature.
I did something like this using <exclude>, but I had to exclude ~ 500 legacy
files, after doing this my ant macker task takes indefinitely. 

Is there another way?

thanks.

Michael.

[macker-user] Catching exceptions

[Doron R. <do...@ra...>]

I want to prevent everyone from catching AssertionError.

 

The problem is, that each:

            assert a > b;

Is actually:

            If (!(a>b))

                throw new AssertionError();

So, everyone uses AssertionError.

 

Thus, my question is: can you add a filter that will match only "catch"
usage, and nothing else?  I do not care if they throw it, create it,
take it, copy it, store it in variables, and so. I just do not want
anyone to catch Errors / Throwables and so.

 

Thanks,

  Doron.

 

 

_______________________________________________

Doron Rajwan, do...@ra..., www.rajwan.org <http://www.rajwan.org/> 

13 Odem street, Rishon Le-Zion, Israel

Home:   03-9512348  [+972-(3)-9512348]

Cell:   064-887732  [+972-(64)-887732]

 

[macker-user] Macker 0.4.2 released

[Paul C. <can...@po...>]

Version 0.4.2 adds a small but significant feature: Macker can now 
generate HTML reports, allowing Macker to function well in an automated 
build (a la AntHill / Cruise Control).  You can generate other types of 
reports as well by writing your own XSLT.  Reports are generated by a 
new Ant task.

Download:
     http://sourceforge.net/project/showfiles.php?group_id=55296

Documentation on the new report feature:
     http://innig.net/macker/guide/report.html

A sample HTML report:
     http://innig.net/macker/guide/report-example/macker-report.html

List of changes in 0.4:
     http://innig.net/macker/whatsnew.html

[macker-user] Preview of HTML reports

[Paul C. <can...@po...>]

Hello all!  I've been working on adding HTML report generation to 
Macker, with lots of help from my cousin Kendall (who got me off on the 
right foot with XSLT).

A working HTML report feature is now checked into CVS, and I'd love to 
have some users try it and give feedback.  The dev version:

     http://innig.net/macker/dist/macker-dev.tar.gz

The new reporting isn't documented yet, so here's a quick start:

* Download & expand archive above
* Go to macker/doc/example/modularity/
* Run "ant macker-report"
* The output tells you where the report was generated
* To see how the generation works, look in:
       macker/doc/example/build-shared.xml

Please send your suggestions!

Cheers,

Paul

Re: [macker-user] Macker 0.4.1: an important bug fix

[Paul C. <can...@po...>]

Xandy --

It's really great to hear that Macker's been useful for you.  It has 
been for us at my workplace (Retek), but it's very encouraging to know 
we're not the only ones.  As much as the programming is fun in itself, 
a sense that it's useful to others is very motivating!

I didn't know (or at least didn't remember) that Scott reports to you.  
You submitted some very helpful patches, but letting him contribute "on 
the clock" is no less important a contribution!

So, in general, thanks a bunch!  Keep your good feedback coming in....

Paul


On Wednesday, August 27, 2003, at 09:40  AM, Xandy Johnson wrote:

> On Tue, Aug 26, 2003 at 01:48:54PM -0500, Paul Cantrell wrote:
>> I'm curious: is anybody out there actually using Macker?
>
> Paul,
>
> We (the Tracker project at FGM) are using Macker, and it has already
> helped us identify inappropriate dependencies that we have then been
> able to remove.  We even had the case where I wrote a rule that passed
> at the time but that was subsequently violated.  Macker helped us
> identify and resolve that right away.
>
> Also, I don't know if you've made the connection yet or if I've
> mentioned it before, but Scott Sayles reports to me, so his involvement
> was sparked by mine.  I also feel good that even though I haven't been
> able to contribute as much as I'd like, I can give him time (i.e. his
> contributions can be "on-the-clock").
>
> Thanks so much for what you're doing.
>
> Xandy
> <mime-attachment>

[macker-user] Macker 0.4.1: an important bug fix

[Paul C. <can...@po...>]

Wouldn't you know it -- a mere three hours after posting the release of  
0.4, I found a fairly serious bug, and had to release a patch right  
away.  Fortunately, it took nearly 24 hours for my original annoucement  
to appear on the JDOM list (wake up, Sourceforge!), and the patch was  
probably already available by the time most of you went to download the  
new version.  Still, I though I'd make a second annoucement just in  
case.

The bug was pretty serious: having a <foreach> anywhere in your rules  
file would cause the build to fail, even if there were no rule  
violations.  Yikes!  I've updated the regression tests to catch this.

I'm curious: is anybody out there actually using Macker?  I never got  
any feedback at all on any of the 0.4 betas....

The bug:
      
https://sourceforge.net/tracker/ 
index.php?func=detail&aid=794536&group_id=55296&atid=476503

Download:
     http://sourceforge.net/project/showfiles.php?group_id=55296

Cheers,

Paul

[macker-user] Macker 0.4 released

[Paul C. <can...@po...>]

A mad Sunday dash of coding has Macker 0.4 out the door.  The 
distribution is available on sourceforge, and the online guide is now 
updated to reflect 0.4.  I fixed a whole bunch of bugs today, but on 
the off chance that you find more, please let me know about them!

Download:
     http://sourceforge.net/project/showfiles.php?group_id=55296

Summary of changes:
     http://innig.net/macker/whatsnew.html

Macker home page:
     http://innig.net/macker/

Thanks to those who helped out with this release!
    http://innig.net/macker/thanks.html

Cheers,

Paul

[macker-user] Macker 0.4b1 now available

[Paul C. <can...@po...>]

I've completed the first beta of version 0.4.  Please download it, and 
start those bug reports coming!

What's new in 0.4:

     http://innig.net/macker/whatsnew.html

Download page:

     http://sourceforge.net/project/showfiles.php?group_id=55296

I don't have acknowledgements for those of you who sent in patches yet 
-- apologies -- I'll be sure to include you in the full release!

Cheers,

Paul

[macker-user] First post!

[Paul C. <can...@po...>]

(-1, Old joke)