#22 Allow to disable metrics on packages and classes (methods)

[Gilles Scokart]

It would be nice to allow to (enable/)"disable" the
metrics on some packages or class.
That would be namely usefull when you have generated
source.

[Frank Sauer]

Logged In: YES
user_id=52904

agreed. I'm looking into this. Question is ALL metrics or do we
need a mechanism that enables certain metrics and disables
others?

[Gilles Scokart]

Logged In: YES
user_id=733250

I think enable/diable all metric at once on a package (or a
class) is better. It's simpler to use. If you use a mechanism
to enable certain metrics on some project, the user will end
with an unknown configuration. He will not know what is
involved in his metrics.

Now disabling some metrics on the view would be nice also.
For instance if a developer don't like the meaning of the DIT
metrics, it should be possible to remove it from the Metrics
View. I will enter an other RFE for that.

[scot mcphee]

Logged In: YES
user_id=630681

As well as, or instead of, a package or class level
disablement, I would like to see the ability to disable at
the source folder level.

For example, I sometimes put generated classes into a
separate source folder (particularly if they are generated
every time a build is run, as in the case of xdoclet
generation), and certainly, my test cases are in a different
source folder, even though the *packages* are the same as
the main source folder. I have found that introducing the
test classes to the metrics causes all sorts of problems. I
would like to simply exclude all classes in the test source dir.

Filename filters would work ok in lieu of this (e.g. exclude
*Test.java) if source folder filtering is not possible.

[LeO]

Logged In: YES
user_id=703323

Is there some progress on this issue? I would like to see
this feature as well.

I could live as well with specifing it in the
Project-properties as some kind of filter what to exclude.
e.g. all packages with containing *test*