include/exclude processing order does not match documentation
-------------------------------------------------------------
Key: CDV-785
URL: https://jira.terracotta.org/jira//browse/CDV-785
Project: Community Development
Issue Type: Bug
Components: Configuration
Affects Versions: 2.6.1
Reporter: Tim Eck
Assignee: Issue Review Board
The docs here:
http://www.terracotta.org/confluence/display/docs1/Configuration+Guide+and+Reference#ConfigurationGuideandReference-%2Ftc%3Atcconfig%2Fapplication%2Fdso%2Finstrumentedclasses
Say this:
The include and exclude stanzas are evaluated bottom up according to the order
in the Terracotta configuration file. The first pattern that matches will
determine whether the class will or will not be instrumented. If no patterns
match, the class will not be instrumented"
In reality this is not true. Consider this config:
<instrumented-classes>
<exclude>foo.Type*</exclude>
<include>
<class-expression>foo.Type2</class-expression>
</include>
</instrumented-classes>
With the above config, foo.Type2 should be included but it is not.
Interestingly enough, the eclipse plugin processes things correctly and
decorates Type2 as included.
I think the product should be updated to match the documentation and the
eclipse plugin. If we're going to make the documentation fit the product then
we're going to have to update the eclipse plugin as well.
The problematic code is in
com.tc.object.config.ConfigLoader.loadInstrumentedClasses()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
