November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21114) Dont stop watch client on disconnect

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21114?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21114: --------------------------------------- [~jcantrill] Please provide information how to verify that it is done. > Dont stop watch client on disconnect > ------------------------------------ > > Key: JBIDE-21114 > URL: https://issues.jboss.org/browse/JBIDE-21114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Should just reconnect on error and leave watchclient running -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20574) Remove "New/Import OpenShift Application" from the Project > Configure... menu

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20574?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20574. --------------------------------- Rewording verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Remove "New/Import OpenShift Application" from the Project > Configure... menu > ------------------------------------------------------------------------------ > > Key: JBIDE-20574 > URL: https://issues.jboss.org/browse/JBIDE-20574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > As reported by [~sspeiche], "New/Import OpenShift Application" doesn't belong to the Project "Configure..." menu. it should be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- Okey, maybe i'm missing something but what has there been spent time on since we last discussed the downsides of this ? Sounds like you said you spend more time besides what we did around the last GA (October) - but I did not see any additions/changes thus my comments haven't changed since then and thus surprised you say you have spent much time on it. Did I miss something ? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21061) Applcation wizard: error message tells me to select server template while I'm about to pick a local template

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21061?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21061. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Applcation wizard: error message tells me to select server template while I'm about to pick a local template > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21061 > URL: https://issues.jboss.org/browse/JBIDE-21061 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: choosing-local-template-wrong-error.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- Well, if you want to discard this change that several other people have approved in the comments here, feel free to do it. It's just a shame you didn't tell me earlier, it would have saved me much time. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- As a normal user and as us wanting to make sure the software the *normal* user install I do not think it is valuable at all to have them see Early access by default. Having a dialog popping up making them select between two options that looks *exactly* identical is not helping the user to understand he is installing something "special"; nor why he needs to make a choice. I think it is perfectly fine to require that users that wants early access to know what early access is. I know you don't like the "advertise" entries - but they solve the problem of being able to show *selectively* relevant info about things even if they are not available as earlyaccess. i.e. this jiras solution don't solve the problem when we get to next year and IS is not available at all. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- both download-maven-plugin and maven-dependency-plugin have cache mechanism that makes that a single file is downloaded only twice. For "runtime" bundles (such as forge, livereload...) consuming jars and zips to work propertly, we never want to skip the download of their inner parts. Then, for those, we can simply unset/remove the skip property or force it to false, so we're sure whenever they build their runtime are copied where necessary (and fetched if necessary). For "tests" bundles, I believe (I'm less sure) that it's about the same: whenever one is going to run the tests, the the artifacts need to be downloaded. So I believe we can set in such bundles (or in their parent pom in component/tests for better factorization) skip=skipTests. Since maven-download-plugin already provides the mdep.skip property and download-maven-plugin provides a download.plugin.skip properties, here are the concrete step I suggest: # Remove the skipRequirements in parent pom https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... # Remove default setting of skip on line 509 and 519 # In components/tests/pom.xml for components that have test requiring runtimes, add {code:xml} <properties> <mdep.skip>${skipTests}</mdep.skip> <download.plugin.skip>${skipTests}</download.plugin.skip> </properties> {code} > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21062) Context menu items to trigger a new build containg incorrect label

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21062?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21062. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Context menu items to trigger a new build containg incorrect label > ------------------------------------------------------------------ > > Key: JBIDE-21062 > URL: https://issues.jboss.org/browse/JBIDE-21062 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > In OpenShift Explorer view, context menu to start a new build from existing build config is shown as "Start Build..." and context menu to clone an existing build is "Clone Build...". Both should omit "..." part, because there is no further user interaction needed nor user is prompted. It should be "Start Build" and "Clone Build". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21000) Appliaction wizard: "Remove" button in Resource Labels page should be "Remove..."

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21000?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21000. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Appliaction wizard: "Remove" button in Resource Labels page should be "Remove..." > --------------------------------------------------------------------------------- > > Key: JBIDE-21000 > URL: https://issues.jboss.org/browse/JBIDE-21000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: bad-remove-button-label.png > > > Remove button located on the 3rd New OpenShift Application wizard page (the one with resource labels) should have label "Remove..." instead of "Removed". It's because there is invoked dialog for removal confirmation of a label. If it would be Remove, then no confirmation would be expected. We use this approach all over the wizards and dialogs - if there is expected further user interaction, the "..." should follow a label. > !bad-remove-button-label.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20849. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015