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
i18n properties in JSF project on IntelliJ #260
Comments
It should work. I have no issue with it. Properties reloading is done both in Mojarra and MyFaces plugins. What app server are you using? |
i'm using wildfly 13 Is there any way to see if the file is being picked-up by the hotswap agent? In jrebel, for example, we have a info on the log saying "the file xyz is being reloaded on path/of/the/file" |
uhmmmmmm! Is there any documentation to help me how to develop this? ehehehe It will be a nice feature for adding, i use WF and i can help if you want. |
If you are still interested, please can contact me by email. |
Yes, i'll send a message. Just for better understanding: The wildfly plugin doesn't support reload any resource of JSF like managed beans, i18n resources? CDI beans with |
Should be fixed in 1.3.1.SNAPSHOT. |
Could you check it please? |
I will try, when you are planning to launch the 1.3.1-SNAPHOT? |
We have no deadlines, but it shouldn't be this year :) Btw I'm updating SNAPSHOTs continuously |
I've meant the (1.3.1-SNAPSHOT)[https://github.com/HotswapProjects/HotswapAgent/releases/tag/1.3.1-SNAPSHOT] is updated continuously, so could you check it please? |
Im trying to make hotswap agent 1.3 + dcevm on JDK 8u172 reload my i18n properties files after the edition process on intellij but until now, no way to make this thing work...
I defined the propoerties on the agent properties file but i don't know if the way i do will work:
I tryed to do in the same way like jrebel, but no hotswap for i18n properties... The project root variable is replaced by the maven resources pluign when i build the project and is a direct reference to the ${basedir} variable from maven..
Any advice?
The text was updated successfully, but these errors were encountered: