AnsweredAssumed Answered

Extending ELResolver results in compilation errors

Question asked by jestersuez on Oct 22, 2014
Latest reply on Oct 24, 2014 by jbarrez
Hello,
we currently embed activiti-engine (5.14) as the new rule engine of an administration tool. Part of the integration solution is a custom ELResolver, that is added within ExpressionManagement.createELResolver() and the corresponding CustomResolverFactory, that is added to the CustomProcessEngineConfiguration.resolverFactories. But while this works perfectly inside local eclipse environments, it produces compilation errors on our jenkins server:

[ERROR] \bpm\CustomProcessEngineConfiguration.java:[83,105] error: cannot find symbol
[ERROR] \bpm\CustomResolverFactory.java:[12,61] error: cannot access ELResolver

The cause seems to be related to the package of ELResolver - org.activiti.engine.impl.javax.el - which is not exported within the MANIFEST.MF of activiti-engine, but is only refered to by "uses"-Statements. Possibly I could fix it by manually editing the MANIFEST…but there is certainly be a better solution, right?

Thanks for any help.

Regards, Oliver

Outcomes