July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20390) Port forwarding wizard: should refuse to try to forward ports on "Pending" pods

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-20390: ---------------------------------------- Summary: Port forwarding wizard: should refuse to try to forward ports on "Pending" pods Key: JBIDE-20390 URL: https://issues.jboss.org/browse/JBIDE-20390 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Andre Dietisheim One cannot forward ports for pods which didnt reach the "Running" state. So if you pods are still "Pending" you wont be able to forward ports. The wizard should tell you that before starting a session, it should check the state of the pod and refuse to let you "Start All". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20390) Port forwarding wizard: should refuse to try to forward ports on "Pending" pods

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20390?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20390: ------------------------------------- Fix Version/s: 4.3.0.CR1 > Port forwarding wizard: should refuse to try to forward ports on "Pending" pods > ------------------------------------------------------------------------------- > > Key: JBIDE-20390 > URL: https://issues.jboss.org/browse/JBIDE-20390 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.CR1 > > > One cannot forward ports for pods which didnt reach the "Running" state. So if you pods are still "Pending" you wont be able to forward ports. The wizard should tell you that before starting a session, it should check the state of the pod and refuse to let you "Start All". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18709?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-18709: -------------------------------------- This is correct. We screwed up the server response in order to be compatible with the current version of JBoss Tools. > EAP alpha releases not require credentials; verify downloadRuntimes works > ------------------------------------------------------------------------- > > Key: JBIDE-18709 > URL: https://issues.jboss.org/browse/JBIDE-18709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release. > We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20376: ------------------------------------------ I think that this is critical since the root problem here is that the tooling wont detect that a port forwarding session already exists. The 2nd call then would always fail. > [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20376: ------------------------------------- Priority: Critical (was: Major) > [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20376: ------------------------------------- Fix Version/s: 4.3.0.CR1 > [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-647) Update JBDS 9.0.0 Install doc with info for offline zip

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-647?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-647: -------------------------------------------- > Spoke to Radim today who says that the user will need only one zip file (Update Site Zip) for the offline installation > Made changes in the topic accordingly (41914) > Created a QE JIRA for Jan to review the topic (JBQA-12310) > Review complete > added entry to rev history topic > Update JBDS 9.0.0 Install doc with info for offline zip > ------------------------------------------------------- > > Key: TOOLSDOC-647 > URL: https://issues.jboss.org/browse/TOOLSDOC-647 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.3.0.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > Change info in the Install JBoss Developer Studio BYOE when Offline section of the JBDS 9.0.0 Install guide to say that the user will need only one .zip (update archive) to install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19795) Bower support

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19795. ------------------------------ Verified in JBT 4.3.0.Beta2. > Bower support > ------------- > > Key: JBIDE-19795 > URL: https://issues.jboss.org/browse/JBIDE-19795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > Need to have initial [Bower|http://bower.io/] tools support: > *The gist* > Bower tooling should initially support several bower API commands : > |Command||Description| > | *bower init* |creates a *bower.json* file| > |*bower install <package>*|installs packages to *bower_components* folder| > |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory| > |*bower update* |updates installed packages to their newest version according to *bower.json*| > Basically, the main idea of the implementation is the following: > Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration* > Native bower tools must be preinstalled > *The main questions & proposals:* > 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.) > 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature? > 3. Implementation details: > - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) > - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20373) [origin_intservice_57] Application wizard: Failed to show the summary of generated values to new app

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20373?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20373: --------------------------------------- [~adietish] I think it is valid to report empty values as empty might be a valid entry for someone's parameter. In regards to 'do we show if we fail to create resources'...I believe we have to because it's not an atomic operation; there is no way to role back what you have done. You could get successfully create some resources which utilize the values. > [origin_intservice_57] Application wizard: Failed to show the summary of generated values to new app > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20373 > URL: https://issues.jboss.org/browse/JBIDE-20373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: generated-values.png, Screenshot1.png, Screenshot2.png, Screenshot3.png > > > It's failed to show the summary of generated values to new app -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20258) Replace label 'Create artifact' in batch property editor with a specific artifact name

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20258?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20258. ----------------------------------- Verified JBDS 9 beta2b > Replace label 'Create artifact' in batch property editor with a specific artifact name > -------------------------------------------------------------------------------------- > > Key: JBIDE-20258 > URL: https://issues.jboss.org/browse/JBIDE-20258 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.2.3.Beta1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > When attribute 'ref' is empty or targeted artifact does not exist, assist menu at the field contains a create action. Now it has common label 'Create artifact'. It will be better to specify what artifact may be created, e.g. 'Create batchlet'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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