August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-374) Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-374?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-374: ------------------------------ Sprint: devex #118 July 2016 > Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121] > --------------------------------------------------------------------------------------------------- > > Key: ERT-374 > URL: https://issues.jboss.org/browse/ERT-374 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > When starting up an Eclipse session that had the Docker Explorer view and one or both of the Docker Containers view and Docker Images view, a default connection will be selected, but the Containers and Images view will not fill in their tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-374) Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-374?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-374: --------------------------------- Assignee: Jeff Johnston > Docker Containers View and Docker Images View do not fill in automatically at start up [EBZ#499121] > --------------------------------------------------------------------------------------------------- > > Key: ERT-374 > URL: https://issues.jboss.org/browse/ERT-374 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > When starting up an Eclipse session that had the Docker Explorer view and one or both of the Docker Containers view and Docker Images view, a default connection will be selected, but the Containers and Images view will not fill in their tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22673: ------------------------------------ I have reached out to the tycho-user@ list to find out when 0.26 might be released: http://dev.eclipse.org/mhonarc/lists/tycho-user/msg07403.html > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22611: ------------------------------------ Depends on Tycho 0.26 so slip to 4.4.2. > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.2.AM1 > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22611: ------------------------------- Sprint: (was: devex #118 July 2016) > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.2.AM1 > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22673: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.AM3) > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22611: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.AM3) > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.2.AM1 > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22581: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.x) > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM1 > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22862) Example "." found when searching for a Camel quickstart

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22862?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22862: ------------------------------------- [~lkrzyzanek] the query is http://dcp2.jboss.org/v2/rest/search?size=500&content_provider=jboss-deve... The faulty example is: {noformat} {"_index":"data_jbossdeveloper_quickstart","_type":"jbossdeveloper_quickstart","_id":"jbossdeveloper_quickstart-7bd1603e","_score":1.0,"fields":{"git_download":["https://github.com/jboss-fuse/quickstarts/archive/6.2.1.GA.zip"],"sys_description":["These quickstarts demonstrate a variety of ways to get started with Fuse and many of it's technologies"],"sys_tags":["Camel","CXF","REST","SOAP"],"sys_type":["quickstart"],"target_product":["fuse"],"github_repo_url":["https://github.com/jboss-fuse/quickstarts"],"quickstart_id":["."],"experimental":[false],"git_tag":["6.2.1.GA"],"git_commit":["c6243b5"],"sys_title":["quickstarts: Various quickstarts to demonstrate Fuse"]}} {noformat} > Example "." found when searching for a Camel quickstart > ------------------------------------------------------- > > Key: JBIDE-22862 > URL: https://issues.jboss.org/browse/JBIDE-22862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.4.1.AM1 > Environment: JBoss Fuse Tools must be installed > Reporter: Fred Bricon > > When the JBoss Fuse tools are installes, the Camel examples are available in JBoss Central. If you search for Camel, An example named "." is returned. It fails to import. > See !http://content.screencast.com/users/fbricon/folders/Jing/media/36fb717a-1cd8-4c6a-8c25-b74d46c4c6be/00000447.png|width=700! > That example should not be returned. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) wrap new devstudio-javaee update site inside an rpm for linux installs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3982: ----------------------------- Fix Version/s: 10.1.0.AM3 > wrap new devstudio-javaee update site inside an rpm for linux installs > ---------------------------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.AM3 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016