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

Detect code-changes in FastTags and JavaExtentions #2

Open
mbknor opened this issue Mar 7, 2012 · 0 comments
Open

Detect code-changes in FastTags and JavaExtentions #2

mbknor opened this issue Mar 7, 2012 · 0 comments

Comments

@mbknor
Copy link
Owner

mbknor commented Mar 7, 2012

Almost all code changes works as it should: changed templates and changed app code.

But when using GTFastTag or JavaExtentions there is a problem with changes.

The special-case here is that the template code is calling back into the app code.

Since this is currently done using a fixed classloader, we still see the old verison of the class, even though play2 has been "restarted" and is now using a new classloader.

This must be fixed.. But must prevent recompilation of the templates

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

No branches or pull requests

1 participant