|
|
|
[
Permlink
| « Hide
]
Marcus Brito - 14 Nov 05 16:16
See IDEA-5783 for a different view on the same problem.
I'm in some doubt about desired IDEA's behaviour in the described case. There are three cases:
a) "Deploy after compilation" option is set to "Always'". In this case IDEA will perform redeploying the application instead of reloading the classes (because IDEA-5783 is already fixed) so everything is all right. b) "Deploy after compilation" option is set to "Ask". IDEA will ask about redeploying and only in case of refusal reloading the classes will be performed. Are you sure that IDEA should ask about redeploying again after failing of reloading the classes? c) "Deploy after compilation" option is set to "Never". Should IDEA redeploy silently the application after failing? Or ask to redeploy? Hmm, tricky question. Maybe we need a new option? I can imagine the most useful option for me would be one where IDEA would always try to reload changed classes, and when that fails, automatically redeploy the application. Here's what I think should happen:
a) "Deploy after compilation" will always redeploy the application b) "Ask": same as above, but instead of silently redeploying the application, IDEA would ask the user first. c) "Never": if reloading fails, IDEA warns the user about it and does nothing. |
|||||||||||||||||||||||||||||||||||||||||||||