[JBoss JIRA] (JBIDE-17408) jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0

Tuesday, 10 June 2014

    [
https://issues.jboss.org/browse/JBIDE-17408?page=com.atlassian.jira.plugi...
] 

Vlado Pakan commented on JBIDE-17408:
-------------------------------------

There is no version conflict in JBDS because old version of org.jboss.tools.jst.jsdt with
no specific version restriction for tern plugins. And that is not correct am I right?

Scenario:

1. Install JBDS
2. Install HMT from JBDS Central - it installs old version of org.jboss.tools.jst.jsdt:
Version: org.jboss.tools.jst.jsdt_3.6.0.Beta2-v20140523-1522-B35.jar. This version has no
specific version restriction for tern plugins only 0.2.0 is set as minimal version
3. Install tern from http://oss.opensagres.fr/tern.repository/0.2.0. Version:
0.2.0.201405272009

ERROR: There is no version conflict. I think HMT should install never version of
org.jboss.tools.jst.jsdt plugin

...
 jst.jsdt plugin should depend on SPECIFIC version of tern.java, not
just 0.2.0
 ------------------------------------------------------------------------------

                 Key: JBIDE-17408
                 URL: https://issues.jboss.org/browse/JBIDE-17408
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: jsp/jsf/xml/html source editing
    Affects Versions: 4.2.0.Beta2
            Reporter: Nick Boldt
            Assignee: Victor Rubezhny
              Labels: respin-b
             Fix For: 4.2.0.Beta2

 Max says (paraphrasing):
 "The JSDT stuff should be locked down so that it depends on a specific version of
tern.java, not just any version. We want it so that users can only install the version of
tern.java we include in our TP."
 Currently, this is 0.2.0.201405210810. 

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006