[jbosstools-issues] [JBoss JIRA] (JBIDE-21997) Update TP to include newer version of aeri

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21997:
------------------------------------

So you want me to pull the latest not-quite-released Neon.M6 version [1] of AERI into our Mars.2 target platform? I'm not sure that's a good idea. 

[1] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedule

[~marcel.bruch] can you comment here? Is it safe to pull neon/201603301000/plugins/org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar into our Mars.2-based target platform? Is it backward compatible with Mars.2 bits?

(Unrelated but curious... anyone know how there's a neon/20160330 folder already created on Mar 29? Did this past Friday's release slip to tomorrow because of Easter?)

> Update TP to include newer version of aeri
> ------------------------------------------
>
>                 Key: JBIDE-21997
>                 URL: https://issues.jboss.org/browse/JBIDE-21997
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: aeri, target-platform
>    Affects Versions: 4.3.1.CR1
>            Reporter: Aurélien Pupier
>            Priority: Critical
>             Fix For: 4.3.1.Final
>
>
> an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling.
> We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868 
> Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103
> Please take care because the version number are both 1.100.0



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)