[jbosstools-issues] [JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-24966:
-------------------------------
    Description: 
Turns out we have a blocker here.

org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.

Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2:

{code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
Require-Bundle: org.junit,org.eclipse.swt,
org.eclipse.ui,
org.eclipse.osgi,org.eclipse.core.runtime,
org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
org.jboss.reddeer.common;bundle-version="1.2.1", <<
org.jboss.reddeer.swt;bundle-version="1.2.1", <<
org.jboss.reddeer.core;bundle-version="1.2.1", <<
org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
org.apache.commons.lang;bundle-version="2.6.0",
org.eclipse.linuxtools.docker.core,
org.hamcrest.library;bundle-version="1.3.0",
org.hamcrest.core;bundle-version="1.3.0"{code}

Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance. 

  was:
Turns out we have a blocker here.

org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.

Therefore this manifest needs to be changed:

{code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
Require-Bundle: org.junit,org.eclipse.swt,
org.eclipse.ui,
org.eclipse.osgi,org.eclipse.core.runtime,
org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
org.jboss.reddeer.common;bundle-version="1.2.1", <<
org.jboss.reddeer.swt;bundle-version="1.2.1", <<
org.jboss.reddeer.core;bundle-version="1.2.1", <<
org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
org.apache.commons.lang;bundle-version="2.6.0",
org.eclipse.linuxtools.docker.core,
org.hamcrest.library;bundle-version="1.3.0",
org.hamcrest.core;bundle-version="1.3.0"{code}




> linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-24966
>                 URL: https://issues.jboss.org/browse/JBIDE-24966
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, docker, target-platform
>    Affects Versions: 4.5.1.AM2
>            Reporter: Nick Boldt
>            Assignee: Jeff Johnston
>            Priority: Blocker
>             Fix For: 4.5.1.AM2
>
>
> Turns out we have a blocker here.
> org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.
> Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2:
> {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
> Require-Bundle: org.junit,org.eclipse.swt,
> org.eclipse.ui,
> org.eclipse.osgi,org.eclipse.core.runtime,
> org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
> org.jboss.reddeer.common;bundle-version="1.2.1", <<
> org.jboss.reddeer.swt;bundle-version="1.2.1", <<
> org.jboss.reddeer.core;bundle-version="1.2.1", <<
> org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
> org.apache.commons.lang;bundle-version="2.6.0",
> org.eclipse.linuxtools.docker.core,
> org.hamcrest.library;bundle-version="1.3.0",
> org.hamcrest.core;bundle-version="1.3.0"{code}
> Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)