[jira] Created: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Reporter: Paul Spencer Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
[ https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Spencer updated SHALE-446: --- Affects Version/s: 1.1.0-SNAPSHOT Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: Paul Spencer Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
[ https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Spencer updated SHALE-446: --- Attachment: shale-446.patch Add Cobertura plugin version number Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: Paul Spencer Attachments: shale-446.patch Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
[ https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Spencer updated SHALE-446: --- Flags: [Patch] Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: Paul Spencer Attachments: shale-446.patch Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
[ https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41008 ] Hermod Opstvedt commented on SHALE-446: --- DId you try to do this: mvn -U clean install. Note the -U which will force an update check of the plugins. This is a Maven issue, and your suggested fix is just a workaround. It vill also lock down the versionnumber to a specific version instead of the latest release. Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: Paul Spencer Attachments: shale-446.patch Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
