You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/02/20 12:52:11 UTC

[jira] [Resolved] (SLING-4094) Handle PropertyType.UNDEFINED when updating properties

     [ https://issues.apache.org/jira/browse/SLING-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-4094.
------------------------------------
    Resolution: Fixed

> Handle PropertyType.UNDEFINED when updating properties
> ------------------------------------------------------
>
>                 Key: SLING-4094
>                 URL: https://issues.apache.org/jira/browse/SLING-4094
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.4
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Minor
>             Fix For: Sling Eclipse IDE 1.0.6
>
>
> When synchronizing properties we check if the existing property type and the new property type match. If they don't we remove the existing property.
> However, AFAIU from the Javadocs we should not do that for PropertyType.UNDEFINED, as
> {quote}This constant can be used within a property definition (see 4.7.5 Property Definitions) to specify that the property in question may be of any type. However, it cannot be the actual type of any property instance. {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)