You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since COPPER 3.0-RC.5, COPPER advertises that it can use ecj to transform workflow classes when FileBasedWorkflowRepository is used. (My fault, I wrote that... :-} However, this is not true.
ecj creates slightly different bytecode, which the byte code transformer cannot transform.
It would be nice if ecj works as advertised, because then it's possible to run COPPER on a plain JRE without tools.jar. And you still have the possibility of hot deployment, as opposed to when using ClasspathWorkflowRepository.
The text was updated successfully, but these errors were encountered:
Since COPPER 3.0-RC.5, COPPER advertises that it can use ecj to transform workflow classes when FileBasedWorkflowRepository is used. (My fault, I wrote that... :-} However, this is not true.
ecj creates slightly different bytecode, which the byte code transformer cannot transform.
It would be nice if ecj works as advertised, because then it's possible to run COPPER on a plain JRE without tools.jar. And you still have the possibility of hot deployment, as opposed to when using ClasspathWorkflowRepository.
The text was updated successfully, but these errors were encountered: