[jbosstools-issues] [JBoss JIRA] (JBDS-3049) Aerogear feature installation from JBDS central fails

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-3049 at 5/27/14 9:20 PM:
-----------------------------------------------------------

Your assumption is correct:

{code:title=https://github.com/jbosstools/jbosstools-aerogear/blob/jbosstools-4.2.0.Beta2x/cordova/plugins/org.jboss.tools.aerogear.hybrid.core/META-INF/MANIFEST.MF#L23}
Require-Bundle: org.eclipse.core.runtime,
...
 org.apache.httpcomponents.httpclient;bundle-version="[4.2.5,4.3.0)",
 org.apache.httpcomponents.httpcore;bundle-version="[4.2.5,4.3.0)",
 org.jboss.tools.jst.jsdt{code}

So, should Aerogear optionally depend on o.j.t.jst.jsdt? Or should we just add Tern to the JBDS TP so that the deps can be resolved, and o.j.t.jst.jsdt can be installed, too? 

I would vote for fixing the target platform, but I got kinda yelled at the last time I suggested that. :(

So... the current workaround to *BUILD* JBDS is this:

https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L87-L92

We could implement a similar workaround by sticking the Tern site [1] into the composite site [2] that includes the JBDS TP, so it's resolvable even if it's not strictly *IN* the target platform definition and site. 

[1] http://download.jboss.org/jbosstools/updates/requirements/tern/0.2.0.201405210810-SNAPSHOT/ 

[2] https://devstudio.jboss.com/updates/8.0-staging/ composite*.xml


was (Author: nickboldt):
Your assumption is correct:

{code:title=https://github.com/jbosstools/jbosstools-aerogear/blob/jbosstools-4.2.0.Beta2x/cordova/plugins/org.jboss.tools.aerogear.hybrid.core/META-INF/MANIFEST.MF#L23}
Require-Bundle: org.eclipse.core.runtime,
...
 org.apache.httpcomponents.httpclient;bundle-version="[4.2.5,4.3.0)",
 org.apache.httpcomponents.httpcore;bundle-version="[4.2.5,4.3.0)",
 org.jboss.tools.jst.jsdt{code}

So, should Aerogear optionally depend on o.j.t.jst.jsdt? Or should we just add Tern to the JBDS TP so that the deps can be resolved, and o.j.t.jst.jsdt can be installed, too? 

I would vote for fixing the target platform, but I got kinda yelled at the last time I suggested that. :(

So... the current workaround to *BUILD* JBDS is this:

https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L87-L92

We could implement a similar workaround by sticking the Tern site into the composite site that includes the JBDS TP, so it's resolvable even if it's not strictly *IN* the target platform definition and site.

> Aerogear feature installation from JBDS central fails
> -----------------------------------------------------
>
>                 Key: JBDS-3049
>                 URL: https://issues.jboss.org/browse/JBDS-3049
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: aerogear-hybrid
>    Affects Versions: 8.0.0.Beta2
>            Reporter: Denis Golovin
>            Assignee: Nick Boldt
>              Labels: respin-a
>             Fix For: 8.0.0.Beta2
>
>
> Currently Aerogear plug-ins requires jst.jsdt plugins which in turn depends on tern.java plug-ins. JBDS has no tern plugins in TP and it leads to errors in dependencies resolution.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)