[
https://issues.jboss.org/browse/JBIDE-17211?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-17211.
---------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.2.0.CR1)
Resolution: Done
I've made a commit which changes a few subtle things:
1) The scanner interval and scanner timeout now live UNDER "Add missing
scanners" and above "Remove added scanners".
2) The two labels for scanner interval and timeout are now indented, to make clear these
are settings only on the added scanners
3) The two labels now say "Added scanner timeout" and "Added scanenr
interval"
4) I noticed that if you unchecked "Add missing blahblah" and then did a
ctrl+z, the checkbox was not re-checked. This is because the wrong default value was
assumed. This has been fixed.
Inform users which deployment scanner's interval they're
setting
----------------------------------------------------------------
Key: JBIDE-17211
URL:
https://issues.jboss.org/browse/JBIDE-17211
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta2
You asked for a new JIRA in JBIDE-15287 so here you go :)
It is possible to change the interval for the custom deployment scanners that the tools
add.
But the UI doesn't state this, so it seems that in fact we alter the interval even
for the default deployment scanner which we don't.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)