|
||||||||
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-791) After updating jbeh... Maciej Madej (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Maciej Madej (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Maciej Madej (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Maciej Madej (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Maciej Madej (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-791) After updating... Maciej Madej (JIRA)
Not sure what the problem is here. When you upgrade from 3.5.4 to 3.6.7 a bug is fixed.
Why do you say it's a critical issue for you?