Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

if ecj is found in classpath, workflow classes cannot be transformed #52

Open
dmoebius opened this issue Oct 19, 2015 · 0 comments
Open
Assignees
Labels

Comments

@dmoebius
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants