Re: [macker-user] legacy code problem

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

Michael --

Unless there's some consistency to the packaging or naming of your 
legacy classes, I'm afraid there's no better way.

How do you distinguish the legacy classes yourself?  Are they in a 
separate source tree?

Paul


On Dec 31, 2003, at 9:36 AM, Michael Davidovich wrote:

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