[jbosstools-issues] [JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011045#comment-13011045 ] 

Mickael Istria commented on JBIDE-18595:
----------------------------------------

We have SR1 included (more precisely, it's SR1 RC4, which only has for difference a resource file in org.eclipse.platform that doesn't have any impact on JBDS).
So JBDS has the bug, but so far, no use-case was reported showing that we have an execution path triggering the bug. What would be a scenario to reproduce the issue? I guess QE would have noticed this error if it were present in main JBDS use-cases.

> Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18595
>                 URL: https://issues.jboss.org/browse/JBIDE-18595
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven, target-platform
>            Reporter: Max Rydahl Andersen
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract.
> Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging)



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)