Yes, this was brought in via transitive dependencies; it's not
explicitly in the target platform [1].
[1]
https://github.com/jbosstools/jbosstools-target-platforms/blob/4.30.x/jbo...
Meanwhile, another ecf-related problem has appeared, apparently related
to the new Foundation:
https://issues.jboss.org/browse/JBDS-2657
On 06/07/2013 10:01 AM, Mickael Istria wrote:
On 06/07/2013 02:48 PM, Max Rydahl Andersen wrote:
> Doesn't this require a fix in our TP also or is this all done via
> transitive dependencies ?
I think it's the other way round: updating TP revealed this change in
Bundle-SymbolicName and then requires a fix in consumers.
As we include this bundle as part of a feature, this is not something
that is visible in target platform definition.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com