[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-18422:
-----------------------------------------
I don't think this exception is regression and/or blocker. I've created an issue on GitHub regarding this exception: https://github.com/angelozerr/angularjs-eclipse/issues/106
The exception is result of execution of a request to Tern server (a responce from the Tern server), so it's handled by Tern.java by logging it into the Error Log.
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18422:
----------------------------------------
{quote}
Exception from comment above exists already in previous version of Tern 0.6.0.201409041810 used with JBT 4.2.0.CR1 so it's not regression. Should I create separate Jira for it?
{quote}
Yes, please.
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17895:
------------------------------------
General policy for our stuff has been to REQUIRE the .0 release (Kepler R, Luna R) but RECOMMEND the latest .1 / .2 (SR1 / SR2) maintenance release.
For example:
{code:title=https://marketplace.eclipse.org/content/jboss-tools-kepler}
Eclipse 4.3 (Kepler) is required. Eclipse 4.3.2 (Kepler SR2) is recommended.
{code}
So... as you say, we can't avoid this problem in JBT 4.2.0, but we can ENCOURAGE users to find a solution to it by simply upgrading to the latest Luna SR. (And for JBDS we can force the update by including the latest content in the target platform, but again, that only applies to installer users, not BYOE / Marketplace users.)
> Consume wtp patch build (update to Luna SR1)
> --------------------------------------------
>
> Key: JBIDE-17895
> URL: https://issues.jboss.org/browse/JBIDE-17895
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, server, target-platform, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351
> The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141...
> However, I'm not sure that's the ultimate location for the future.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18415) Forge New Project wizard - no Archetype catalogues listed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18415?page=com.atlassian.jira.plugi... ]
George Gastaldi reassigned JBIDE-18415:
---------------------------------------
Assignee: George Gastaldi
> Forge New Project wizard - no Archetype catalogues listed
> ---------------------------------------------------------
>
> Key: JBIDE-18415
> URL: https://issues.jboss.org/browse/JBIDE-18415
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
> Assignee: George Gastaldi
>
> Forge 2 New Project wizard lists no catalogs for 'From Archetype Catalog' project option.
> * Ctrl+4
> * New Project
> * Project name: blah
> * Project type: From Archetype Catalog >> no options for Catalog or Archetype
> Could this list be populated by Preferences > Maven > Archetypes > Archetype Catalog Table? And have a link in the wizard to this preference page for users to quickly add another catalog? (Like the OpenShift wizard has a link to SSH Preferences for adding private key to IDE in middle of wizard.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months