August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3965: ------------------------------------- Problem is the message cannot be static. It depends on what was installed. What if user have not installed DevStudio, but CDK only, or vice versa? [~tmancini] suggested to change the link to devsuite produc get-started page and populate it with get-started documents related to products installed: "The getting started page for DevSuite could just be a catalog of the Getting Started pages for the products that it installs (DevStudio, CDK, OpenJDK, etc.) I will even commit to the URL being: http://developers.redhat.com/products/devsuite/get-started/". The message could be about DevSuite: "Congratulations, your installation is finished. You can start using Red Hat Development Suite now by launching installed products <list of buttons to launch DevStudio or cmd in cdk\bin> For more information, see <link to online guide>" If no launchers provided then 'You can start' part should not appear at all. There is JBDS-3732 with similar request. > Add a note on how to launch cdk in last page of devsuite installer > ------------------------------------------------------------------ > > Key: JBDS-3965 > URL: https://issues.jboss.org/browse/JBDS-3965 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk. > This is described here: JBIDE-22734 > What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon. > Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View. > So here's a proposal: > Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched? > Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22888) update the versions of SVNKit and Subclipse we bundle in Red Hat Central.

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22888?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-22888: --------------------------------------- Red Hat Central includes the pure Java SVNKit adapter, but doesn't include the JNA SVNKit adapter. In my opinion, that is correct because the JNA SVNKit adapter can be the cause of different issues. We could update the subclipse connector, but shouldn't include the JNA (JavaHL) SVNKit adapter. I suppose Fabrizio has installed subclipse using the subclipse update site that includes both of the SVNKit adapters, JNA and Java, which is, probably, the reason why our QE team hasn't faced this issue. > update the versions of SVNKit and Subclipse we bundle in Red Hat Central. > ------------------------------------------------------------------------- > > Key: JBIDE-22888 > URL: https://issues.jboss.org/browse/JBIDE-22888 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central-update, target-platform, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > We could consider updating the versions of SVNKit and Subclipse we bundle in Red Hat Central. > > Currently we have: > * Subclipse 1.10.9 / clientadapter 1.10.3 > * svnkit 1.8.10 (supports up to svn 1.8) > Latest: > * Subclipse 1.12 > * svnkit 1.8.12 (supports up to svn 1.9 - http://svn.svnkit.com/repos/svnkit/tags/1.8.12/CHANGES.txt) > > Reason to update: https://developer.jboss.org/message/961176?et=watches.email.thread#961176 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22887) Update Docker Tooling in DevStudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22887?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22887. ------------------------------ Fix Version/s: 4.4.1.Final Resolution: Duplicate Issue Dupe of JBIDE-22885 > Update Docker Tooling in DevStudio > ---------------------------------- > > Key: JBIDE-22887 > URL: https://issues.jboss.org/browse/JBIDE-22887 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Please update Docker Tooling in DevStudio: in latest nightly build of DevStudio(Build id: AM3-v20160805-0433-B5701) is version of Docker Tooling from June. > Could affect OpenShift: [~fbricon] [~adietish] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22680: --------------------------------- Original Estimate: (was: 3 days) Remaining Estimate: (was: 3 days) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > Fix For: 4.4.x > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22872) Create integration tests PR check job for mylyn

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22872?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22872: --------------------------------- Original Estimate: (was: 3 hours) Remaining Estimate: (was: 3 hours) > Create integration tests PR check job for mylyn > ----------------------------------------------- > > Key: JBIDE-22872 > URL: https://issues.jboss.org/browse/JBIDE-22872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.4.x > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22776) Create integration tests PR check job for arquilian

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22776?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22776: --------------------------------- Original Estimate: (was: 3 hours) Remaining Estimate: (was: 3 hours) > Create integration tests PR check job for arquilian > --------------------------------------------------- > > Key: JBIDE-22776 > URL: https://issues.jboss.org/browse/JBIDE-22776 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Len DiMaggio > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22821) foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22821?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22821: -------------------------------- Story Points: 1 Sprint: devex #118 July 2016 > foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22821 > URL: https://issues.jboss.org/browse/JBIDE-22821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.1.AM3 > > > foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either > [~fbricon] should the parser be able to resolve 4.4.1.AM so I can at least differentiate from 4.4.1 or 4.4.1.Final? > Meanwhille, need to figure out why foundation.core thinks it's AM1 and not AM2. jgit timestamps, maybe? -- 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 Libor Krzyžanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22862?page=com.atlassian.jira.plugi... ] Libor Krzyžanek commented on JBIDE-22862: ----------------------------------------- And regarding wrong data like "." ideally data needs to be fixed rather than filtered out. > 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] (JBIDE-22862) Example "." found when searching for a Camel quickstart

by Libor Krzyžanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22862?page=com.atlassian.jira.plugi... ] Libor Krzyžanek commented on JBIDE-22862: ----------------------------------------- I'm wondering why you don't use "sys_title" field. It is intended to be as title. > 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] (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 resolved ERT-374. ------------------------------- Resolution: Done > 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

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