|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-15617) <st:bind> does... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15617) <st:bind>... jgl...@cloudbees.com (JIRA)
The latter problem is not quite true: <script> is run but in a nonglobal context so any definitions must be prefixed with window. in order to be accessible later.