[ https://issues.jboss.org/browse/JBTM-1322?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1322: -------------------------------- Component/s: Testing -- 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

[ https://issues.jboss.org/browse/JBTM-1322?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1322: -------------------------------- Component/s: Demonstrator -- 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

[ https://issues.jboss.org/browse/JBTM-1322?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1322: -------------------------------- Priority: Major (was: Minor) -- 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

[ https://issues.jboss.org/browse/JBTM-1322?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1322: ------------------------------------- I've searched Google and the only similar case I can find was where someone was incorrectly specifying a different module root location. I think we need to see what's in: C:\hudson\workspace\jbossts-narayana-skipTests\jboss-as\build\target\jboss-as-7.2.0.Alpha1-SNAPSHOT\modules to know what's going on. This of course is long gone. Maybe the AS was still in the process of being built? This could happen if this job was triggered manually, which i believe it was: "Started by anonymous user". I've only seen this happen once. -- 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