[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_41201 ] Paul Spencer commented on SHALE-446: Per Hermod, this is not a Shale issue. You may ignore the patch and close this issue. Paul Spencer 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] 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] Created: (SHALE-404) EL in cond attribute of transation is not properly resolved
EL in cond attribute of transation is not properly resolved
-
Key: SHALE-404
URL: https://issues.apache.org/struts/browse/SHALE-404
Project: Shale
Issue Type: Bug
Components: Dialog
Affects Versions: 1.1.0-SNAPSHOT
Reporter: Paul Spencer
I suspect that SCXML is not getting the properties from dialog.data because the
value of dialog.data.leased is always
false.
***
* Value of dialog.data fields
***
leased = Boolean.TRUE
***
* Dialog configuration for the stat Page 1
***
state id=page1
onentry
shale:view viewId=vehicle/addPage1 /
/onentry
transition event=faces.outcome
cond=${outcome eq 'next' and dialog.data.leased} target=page2 /
transition event=faces.outcome
cond=${outcome eq 'next' and not dialog.data.leased} target=review /
transition target=menu event=faces.outcome
cond=${outcome eq 'cancel'} /
/state
***
* Logging
***
outcome = next
_eventdata = null
_eventdatamap = {faces.outcome=null}
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'next' and dialog.data.leased} = false
_ALL_NAMESPACES = null
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'next' and not dialog.data.leased} = true
_ALL_NAMESPACES = null
_ALL_NAMESPACES = {shale=http://shale.apache.org/dialog-scxml,
=http://www.w3.org/2005/07/scxml}
${outcome eq 'cancel'} = false
_ALL_NAMESPACES = null
_eventdata = null
_eventdatamap = null
Current States: [review]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
