[
https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18595:
----------------------------------------
For JBDS we can probably easily include this patch feature in the .product definition to
have product picking it. We'd just need to remove it from .product when using Luna
SR2.
For JBT, unless we explicitly put a dependency on the patch feature somewhere, then there
is no reason why an Eclipse installation would pick it. I don't think we want to
enforce usage of the patch feature (that might be a source of problems when updating), so
it seems to me that there is nothing perfect we can do on this topic.
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: Task
Components: qa
Affects Versions: 4.2.0.Final
Reporter: Max Rydahl Andersen
Assignee: Len DiMaggio
Fix For: 4.2.1.Final
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.8#6338)