[
https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-17002:
-------------------------------
Attachment: java-8-in-kepler-central-site.png
java-8-in-kepler-central-site2.png
As there were no objections, I've pushed the new plugin out to
http://download.jboss.org/jbosstools/updates/stable/kepler/plugins/ and updated
http://download.jboss.org/jbosstools/updates/stable/kepler/jbosstools-dir...
Just did an install from Central... looks like this:
!java-8-in-kepler-central-site.png!
!java-8-in-kepler-central-site2.png!
----
As to the other issue, all I did was to provide snapshots of the discovery site for 4.1.2
and 4.1.2.1 here:
http://download.jboss.org/jbosstools/discovery/development/
http://download.jboss.org/jbosstools/discovery/stable/
They're not actually linked from anywhere, but are provided for historical purposes in
terms of what QE used to test a given release.
Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
-----------------------------------------------------------
Key: JBIDE-17002
URL:
https://issues.jboss.org/browse/JBIDE-17002
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Affects Versions: 4.1.2.Final
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 4.1.2.Final
Attachments: java-8-in-kepler-central-site.png,
java-8-in-kepler-central-site2.png, jbide17002-3-4-features.png,
jbide17002-6-7-features.png, jbide17002-patch-catg.png
We decided to provide an easy way for JBT users to install Java 8 support in Eclipse
Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP.
* JDT Feature patch :
http://download.eclipse.org/eclipse/updates/4.3-P-builds/
* M2E 1.4.1 (org.eclipse.m2e.feature)
http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905
* WTP Feature Patch :
http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032...
All 3 features should be available via a unique connector in JBoss Central > Software
Updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira