I'm looking at a codebase with a bunch of PaxExam-based integration tests. They all have separate "config" methods annotated with "@Configuration". All of these methods are almost identical, all specifying several identical options. They only vary in the "features()" value.
I believe that PaxExam will look for ALL the methods annotated with "@Configuration" and use the options provided there. The real question is, how does it merge those results, and what would it do with methods in a base class with this annotation? The critical question is whether it will intelligently deal with options that set the same property, but with different values. If the two annotated methods are in the same class, I wouldn't assume any priority, as there's no logical answer to that. However, if one method is in the base class and the other is in the subclass, logic says that the options set in the subclass would override the settings in the base class. I haven't seen any documentation that states how this would work. Is there any specification of this? -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
