Well... that is our use case. I guess what I did not mention (but is implicit) is that there are essentially two mutually exclusive groups here. I see now that there is no support for this as there are tickets regarding grouping of profiles.
I did manage to solve my use case, however. I switched my approach from using profile IDs to active the profile, to using parameters/properties on the command line. So profile A is activated by the absence of a parameter, and profile B is activated by the presence of a parameter. Likewise for profiles C and D. I hope there are plans to increase the flexibility of profiles in future releases. Perhaps the Hamcrest API could easily provide this. Regards, Collin On Fri, Feb 19, 2010 at 4:44 PM, Tobias Gierke < [email protected]> wrote: > > Why do you need to have 4 different profiles ? > > Regards, > Tobias >
