[jbosstools-issues] [JBoss JIRA] (JBIDE-18343) Can't install AngularJS from Central

[Denis Golovin (JIRA)]

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

Denis Golovin edited comment on JBIDE-18343 at 9/16/14 1:26 AM:
----------------------------------------------------------------

Problem is in JBT Early Access TP published in staging area.

In git everything looks right:
 https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L41
and 
 https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.2.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L41
show correct versions for jst features 3.6.0.CR1-v20140911-2133-B68

jst.jsdt is not required to be there, but it shouldn't create any problems.

Early access repo in staging area seems to have binaries built out of previous revision of jbtearlyaccesstarget https://github.com/jbosstools/jbosstools-discovery/commit/a407b2c8f0dc6aa30f243518f6a8dcab860ca722#diff-90b990031d67570ec413035ac95c400dR41 and that's why it has previous version of jst features 3.6.0.CR1-v20140904-0921-B61.

The same problem is in JBDS.

Solution is rebuild jbtearly access target and publish it in staging area.

Assigning to [~mickael_istria] to help with it.
 


was (Author: dgolovin):
Problem is in JBT Early Access TP published in staging area.

In git everything looks right:
 https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L41
and 
 https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.2.x/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target#L41
show correct versions for jst features 3.6.0.CR1-v20140911-2133-B68

jst.jsdt is not required to be there, but it shouldn't create any problems.

Early access repo in staging area seems to have binaries built out of previous revision of jbtearlyaccesstarget https://github.com/jbosstools/jbosstools-discovery/commit/a407b2c8f0dc6aa30f243518f6a8dcab860ca722#diff-90b990031d67570ec413035ac95c400dR41 and that's why it has previous version of jst features 3.6.0.CR1-v20140904-0921-B61.

The same problem is in JBDS.

Solution is rebuild jbtearly access target and publish it in staging area.

Assigning [~mickael_istria] to help with it.
 

> Can't install AngularJS from Central
> ------------------------------------
>
>                 Key: JBIDE-18343
>                 URL: https://issues.jboss.org/browse/JBIDE-18343
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 4.2.0.CR1
>            Reporter: Len DiMaggio
>            Assignee: Mickael Istria
>            Priority: Blocker
>             Fix For: 4.2.0.CR2
>
>         Attachments: angularjs-installation-failure.png, AngularJS_Remediation.png
>
>
> Followup - once the issue in JBIDE-18335 was resolved, attempting to create a new AngularJS project through JBoss Central results in the remediation dialog in the screenshot attached to this JIRA. A reasonable customer expectation would be for all examples created from JBoss Central to work cleanly OOTB without remediation.
> !AngularJS_Remediation.png!
> Things get worse when you try to proceed with the installation, it then crashes with :
> !angularjs-installation-failure.png!



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)