[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23754#action_23754
]
Grégory Joseph commented on MAGNOLIA-2821:
------------------------------------------
Well, these tasks are (supposed to be) very "strict". If a property is supposed
to be absent at the time, the warning is relevant, in the sense that it is an
unexpected situation, and good-citizen tasks are supposed to handle only
expected situations.
Is it just a warning or is the task failing ?
> Do not print warning from PropertyValuesTask when value found is same as the
> one task was supposed to update to
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2821
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2821
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.1
> Reporter: Jan Haderka
> Assignee: Jan Haderka
>
> e.g.
> {code}
> Property "configurationClass" was expected not to exist at
> /modules/data/trees/data, but exists with value
> "info.magnolia.module.data.trees.WorkflowDataAdminTreeConfig" and was going
> to be created with value
> "info.magnolia.module.data.trees.WorkflowDataAdminTreeConfig".
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
