|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Javier A. Ortiz Bultron (JIRA)
- [mojo-dev] [jira] (MNBMODULE-201) ClassNotF... Jesse Glick (JIRA)

If OS tokens are used properly, there should be only one provider enabled at a time. But if that cannot be enforced, e.g. because you are missing architecture tokens, then the interface should define a boolean enabled() method, and then you use lookupAll to find the first provider which should be enabled on the current machine.
In any event you should not be seeing a ClassNotFoundException unless you are doing something wrong with the module system.
Closing since there is no demonstrable problem with the Maven build harness here.