Re: [macker-user] Feature request: Allow to include jar files

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

Hi Etienne. I'm not really clear on what you're asking.

> It would be great if one could add jar files to the macker classpath 
> to be investigated.

Macker will only check for illegal references *from* exploded class 
files.  If for some reason you want to check references from classes in 
a jar, use ant to temporarily expand the jar so Macker can see the 
class files.

But then your example seems to be about *excluding* jar classes, not 
*including* them...?

> When I used the subtype-of feature, macker tried to investigate 
> library classes that I am using in my code. But the library I use is 
> in a jar file and not in a exploded class file folder.

Macker will never give an error like "class X in your library jar 
cannot reference Y" ... but it will give an error like "your class Z, a 
subclass of library class X, cannot reference Y."

> Or is there a way to say that no classes in package x.y.z should be 
> investigated? I could then add my libraries to this exclude path.

You can limit which packages are checked in all kinds of ways.  See the 
user guide.

Perhaps if you can explain you question more specifically, or in a 
different way, your question will be clearer.

Paul