|
||||||||
|
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 |
||||||||
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins plugin... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-853) Jenkins p... Zihao Yu (JIRA)

then it's definitely a new bug.
I cannot reproduce the problem with a sample story I tried, can you please post a shortened sample story that gives you broken XML?