July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22735: -------------------------------- Sprint: devex #117 July 2016 (was: devex #118 July 2016) > CDK Server adapter is not available in Quick Access bar when typing "cdk" > ------------------------------------------------------------------------- > > Key: JBIDE-22735 > URL: https://issues.jboss.org/browse/JBIDE-22735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM2 > > > I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment". > We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22663) Use new Style for FilteredTree

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22663?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-22663: ----------------------------------------- [~mmalina] Where did you try it? I notice that in this bug, there is no mention where the fixed filteredtree was. it is in a MbeanOpenSelectionDialog, but to be honest I even don't know how to open this one. If you checked on "Define a new server" dialog based on the pointed Eclipse bugs, this is normal that there is still the issue as my gerrit change has not been reviewed > Use new Style for FilteredTree > ------------------------------ > > Key: JBIDE-22663 > URL: https://issues.jboss.org/browse/JBIDE-22663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > - it will avoid to have "type search text" entered as a real text and provide a nicer UI > it avoids to have the "type search text" used as a filter when clicking in the text field > for UI difference kind see screenshots on https://bugs.eclipse.org/bugs/show_bug.cgi?id=496805 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22653: -------------------------------- Sprint: devex #119 August 2016 > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22671) Hardcoded docker registry url contains a trailing space

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22671?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22671. --------------------------------- Verified in git. Closing. > Hardcoded docker registry url contains a trailing space > ------------------------------------------------------- > > Key: JBIDE-22671 > URL: https://issues.jboss.org/browse/JBIDE-22671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM1 > > > JBIDE-22441 added a hardcoded url for docker registry url for cdk/openshift. > But there is a trailing space in the url: > https://github.com/jbosstools/jbosstools-openshift/commit/132cea25129ffca... > That looks like an error? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13671. --------------------------------- Closing. > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.1.AM1 > > Attachments: after-jgit.png, after-jgit2.png, arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, before-jgit.png, before-jgit2.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22663) Use new Style for FilteredTree

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22663?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22663: ---------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM1) > Use new Style for FilteredTree > ------------------------------ > > Key: JBIDE-22663 > URL: https://issues.jboss.org/browse/JBIDE-22663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > - it will avoid to have "type search text" entered as a real text and provide a nicer UI > it avoids to have the "type search text" used as a filter when clicking in the text field > for UI difference kind see screenshots on https://bugs.eclipse.org/bugs/show_bug.cgi?id=496805 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22816: ---------------------------------- Summary: Create application from image (or builder) may lead to update being detected Key: JBIDE-22816 URL: https://issues.jboss.org/browse/JBIDE-22816 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Jeff MAURY Fix For: 4.4.1.AM3 When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3965: ------------------------------------- [~dgolovin], I'm not sure exactly what the last installer page looks like right now. But what I had in mind was something like this: Congratulations, your installation is finished. To start using Red Hat Container Development Kit, launch Red Hat JBoss Developer Studio, open the Servers view, select Container Development Environment and click the start button. For more information, see <link to online guide>. [~rick_wagner], what do you think? > 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-22734) Please clarify CDK usage

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22734?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22734. --------------------------------- OK, closing. > Please clarify CDK usage > ------------------------ > > Key: JBIDE-22734 > URL: https://issues.jboss.org/browse/JBIDE-22734 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, docker > Environment: CDK, as used in DevStudio and installed via Development Suite. > Reporter: Rick Wagner > Fix For: 4.4.1.AM2 > > > * * This use case may be attributable to user error. Please weigh implementation cost accordingly. * * > After using the Development Suite installer, the user arrives in a newly installed DevStudio instance but without clear instructions on how to use the CDK. In my first attempt, I relied upon previous CDK experience and went to a command-line to start the CDK with 'vagrant up'. This resulted in a failure of later DevStudio components. > The proper trail is to go to the 'Servers' tab in DevStudio to bring up the environment. (Then DevStudio components like the Docker explorer will properly self-configure. This does *not* happen when the CDK is brought up manually as I had done.) > Please consider, look for ways to prevent other users from taking a similar path. Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-815) Target Platform - 4.4.0.Alpha1 update JBT core 4.4.1.AM2

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-815: -------------------------------- Summary: Target Platform - 4.4.0.Alpha1 update JBT core 4.4.1.AM2 Key: JBTIS-815 URL: https://issues.jboss.org/browse/JBTIS-815 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.4.0.Alpha1-TP Reporter: Paul Leacu Assignee: Paul Leacu *Reason:* Update JBT core to 4.4.1.AM2 *Project page/sources:* *Version:* 4.4.0.Alpha1 *License and owner:* EPL *Original p2 repo:* http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.AM2/ *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* Integration Stack *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} -- 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 July 2016