AnsweredAssumed Answered

Blaze Third Party Lib

Question asked by atdemmin@ruleservices.net on Mar 9, 2017
Latest reply on Mar 14, 2017 by atdemmin@ruleservices.net

Is it true that all JARs in com.fairisaac.eclipse.advisor.thirdparty_VERSION.jar of the Eclipse Plugin are already on the classpath in Eclipse?  In other words, is it true that Eclipse users do not need to add any of these third party jars to their own Eclipse classpath (including Project Properties, Blaze Preferences, or the Eclipse Dropin) for development, they only need to identify what is needed for their runtime classpath for deployment?

 

Also, if they are specifying a different versions of these third party jars in the Eclipse Blaze Advisor Preferences, could it cause conflicts or inconsistent behavior depending on what classes are loaded when running tests in Eclipse?

Outcomes