[
https://issues.jboss.org/browse/JBIDE-11814?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11814:
---------------------------------------------
note: the *latest* is not necessary the correct answer.
newer version could be sneaking in from other sites that are further ahead than eclipse
indigo main target platform so need to be careful.
when regenerating .target file from local cache, ensure TP includes
LATEST when there are more than one version of the same IU present
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-11814
URL:
https://issues.jboss.org/browse/JBIDE-11814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform, updatesite
Affects Versions: 3.3.0.Beta3
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.3.0.CR1
recent updates to TP include watching javax.servlet and jdom backleveling themselves.
This is probably caused by the fact that the TP folder when generated includes multiple
versions of the same IUs:
[12:18:30]nboldt@thunk:~/tru/build/target-platform/JBDS_REPO
$ find . -name "javax.servlet*"
./plugins/javax.servlet.jsp_2.0.0.v201101211617.jar
./plugins/javax.servlet.jsp_2.2.0.v201103241009.jar
./plugins/javax.servlet_2.5.0.v201103041518.jar
./plugins/javax.servlet_3.0.0.v201103241727.jar
[12:18:14]nboldt@thunk:~/tru/build/target-platform/JBT_REPO
$ cd ~/tru/buildfind . -name "javax.servlet*"
./plugins/javax.servlet.jsp_2.0.0.v201101211617.jar
./plugins/javax.servlet.jsp_2.2.0.v201103241009.jar
./plugins/javax.servlet.jsp.source_2.0.0.v201101211617.jar
./plugins/javax.servlet_2.5.0.v201103041518.jar
./plugins/javax.servlet_3.0.0.v201103241727.jar
./plugins/javax.servlet.source_2.5.0.v201103041518.jar
$ find . -name "*jdom*"
./plugins/org.jdom_1.1.1.v201101151400.jar
./plugins/org.jdom_1.0.0.v201005080400.jar
./plugins/org.jdom_jaxen_1.0.0.20081203-1100.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira