April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21439: ------------------------------------ It was decided that we'd skip M6 and go directly to M7. But M7 won't be out until May 6. The TP freeze for Alpha1 will be April 27, so we can code freeze on Apr 28 and release on May 3. So, as long as it's compatible w/ M5, I can pull the latest JSON Editor features into the TP, eg. http://download.eclipse.org/webtools/downloads/drops/R3.8.0/I-3.8.0-20160... http://download.eclipse.org/webtools/downloads/drops/R3.8.0/I-3.8.0-20160... Does that work for you, [~vrubezhny] ? Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Same answer for BOTH JBT and JBDS? Or will it be a new Central connector? > Add JSON Editor to JBDS/JBT Target Platform > ------------------------------------------- > > Key: JBIDE-21439 > URL: https://issues.jboss.org/browse/JBIDE-21439 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Missing description. Need update site from which to fetch IUs, and a list of which IUs to add. > Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21439: ------------------------------- Story Points: 4 Sprint: devex #6 April 2016 > Add JSON Editor to JBDS/JBT Target Platform > ------------------------------------------- > > Key: JBIDE-21439 > URL: https://issues.jboss.org/browse/JBIDE-21439 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Missing description. Need update site from which to fetch IUs, and a list of which IUs to add. > Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21621: ------------------------------------ TP freeze for Alpha1 will be April 27, so we can code freeze on Apr 28 and release on May 3. Which version of Red Deer should be included? > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21621: ---------------------------------- Story Points: 3 Sprint: devex #6 April 2016 Assignee: Nick Boldt > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2044: ---------------------------------- Assigned to [~fbricon] to see if he can kick m2e into accepting my patch in time for Neon M7/RC1. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Story Points: 1 Sprint: devex #6 April 2016 > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Story Points: 2 (was: 1) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.x) (was: 10.x) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2044: -------------------------------- Assignee: Fred Bricon (was: Denis Golovin) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20850: ------------------------------- Story Points: 2 Sprint: devex #6 April 2016 > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016