May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22281) Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22281?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22281: ------------------------------- Priority: Blocker (was: Major) > Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS) > ---------------------------------------------------------------------------- > > Key: JBIDE-22281 > URL: https://issues.jboss.org/browse/JBIDE-22281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > * JBT 4.4.0.Alpha1 loads too many update sites: > 1. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/ > 2. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/discovery.early... > 3. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > 4. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20996: ------------------------------------- I hate to do this, but it seems the most logical answer is for DV to produce an additional installer bundle that comes with EAP or downloads it itself. If DV is the only runtime we have currently that has pre-reqs but doesn't come with them, I'd strongly suggest you ask the DV guys to beef up their installer / bundle to either come with EAP or let the installer download it. > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.x > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20996: -------------------------------- Component/s: upstream > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, upstream > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.x > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22282) Publishing JBDS Central & EA zips is broken

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22282: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Publishing JBDS Central & EA zips is broken > ------------------------------------------- > > Key: JBIDE-22282 > URL: https://issues.jboss.org/browse/JBIDE-22282 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > With the release of JBDS 10.0.0.Alpha1, JBDS central and EA zips not published into https://devstudio.redhat.com/10.0/staging/updates/core/ > Why? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22282) Publishing JBDS Central & EA zips is broken

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22282: ------------------------------- Priority: Blocker (was: Major) > Publishing JBDS Central & EA zips is broken > ------------------------------------------- > > Key: JBIDE-22282 > URL: https://issues.jboss.org/browse/JBIDE-22282 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > With the release of JBDS 10.0.0.Alpha1, JBDS central and EA zips not published into https://devstudio.redhat.com/10.0/staging/updates/core/ > Why? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21065: -------------------------------- Story Points: 3 > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.x > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21065: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha3) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.x > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20711: ------------------------------------- [~mmalina] can you verify you're seeing the same behavior? I admit I'm using wtp source, not built modules... so I'm not sure if this is in current target platform. > Changing deploy-name in component xml file will not take effect > --------------------------------------------------------------- > > Key: JBIDE-20711 > URL: https://issues.jboss.org/browse/JBIDE-20711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.x > > > Steps to replicate: > 1) Create a dynamic web project TestProject > 2) Create a server > 3) Add/Remove action in servers view. You will see the module name is TestProject > 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest) > 5) Add/Remove, note module name didn't change > 6) Publish deployment, note its still deploying as TestProject > 7) Close project, then re-open it > 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar) > 9) Publish, note module is deployed as RobsTest.war -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22419) Deploy Docker Wizard: Connection info looks weird

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22419?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22419: -------------------------------- Priority: Minor (was: Major) > Deploy Docker Wizard: Connection info looks weird > ------------------------------------------------- > > Key: JBIDE-22419 > URL: https://issues.jboss.org/browse/JBIDE-22419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: docker, openshift_v3 > Fix For: 4.4.x > > Attachments: docker_wizard.png > > > Connection info in Deploy Image to OpenShift wizard looks weird. It is a text widget but it looks like it is text area where it is supposed to be text typed, but it is disabled. It is also possible to put cursor there. This apply both for wizard opened via context menu of a docker image as well as for wizard opened from context menu of an OpenShift project. > !docker_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22419) Deploy Docker Wizard: Connection info looks weird

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22419?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22419: -------------------------------- Fix Version/s: 4.4.x > Deploy Docker Wizard: Connection info looks weird > ------------------------------------------------- > > Key: JBIDE-22419 > URL: https://issues.jboss.org/browse/JBIDE-22419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: docker, openshift_v3 > Fix For: 4.4.x > > Attachments: docker_wizard.png > > > Connection info in Deploy Image to OpenShift wizard looks weird. It is a text widget but it looks like it is text area where it is supposed to be text typed, but it is disabled. It is also possible to put cursor there. This apply both for wizard opened via context menu of a docker image as well as for wizard opened from context menu of an OpenShift project. > !docker_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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