October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23352: ------------------------------------------ As examples for explanations in our page I'd took screenshots in the webui, where you're told - for a given docker image that you want to deploy - that the ports are being load balanced (which is what happens in our ui when no route port is selected): !webui-deploy-docker-image.png! We could also explain that we will create a service and a route for the image. Then explaining what serivces and routes offer: !refdoc-services-1.png! !refdoc-services-2.png! > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23384) Include integration-tests in staging and stable update sites

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23384: --------------------------------------- Yes, that's what I meant. > Include integration-tests in staging and stable update sites > ------------------------------------------------------------ > > Key: JBIDE-23384 > URL: https://issues.jboss.org/browse/JBIDE-23384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-23177: --------------------------------------- I can reproduce the issue on JBDS 10.2.0.AM2 and trying to find a fix/workaround. > Server Editor: Combo items have wrong size > ------------------------------------------ > > Key: JBIDE-23177 > URL: https://issues.jboss.org/browse/JBIDE-23177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Labels: openshift_v3, server_editor > Fix For: 4.4.2.AM3 > > Attachments: combos.png > > > When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets. > !combos.png! > Spotted on Fedora 24 with GTK 3. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23374) Update sites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.Final/compositeArtifacts.xml return 404 errors

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23374?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23374: ------------------------------------ [~ldimaggio] Have you seen Nick's comment? Could you, please, close or reopen this issue if needed? > Update sites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... return 404 errors > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23374 > URL: https://issues.jboss.org/browse/JBIDE-23374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.2.AM2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... includes references to: > * http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.Final > * http://download.jboss.org/jbosstools/neon/staging/updates/central/4.4.1.F... > Both of these links return 404 errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23351) Deploy Docker Wizard: Image stream sometimes is not created for local docker images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23351?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23351: ------------------------------------- Fix Version/s: 4.4.x > Deploy Docker Wizard: Image stream sometimes is not created for local docker images > ----------------------------------------------------------------------------------- > > Key: JBIDE-23351 > URL: https://issues.jboss.org/browse/JBIDE-23351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: is_not_created.png > > > When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok. > Following message is shown in resource summary: > !is_not_created.png! > I had checked the checkbox to push to registry. But I am not able to reproduce this all the time. I was able to do it only 2 times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23268) Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.jpt.ui.internal.importer.JPAProjectConfigurator

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23268?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23268. ------------------------------------ > Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.jpt.ui.internal.importer.JPAProjectConfigurator > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23268 > URL: https://issues.jboss.org/browse/JBIDE-23268 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.2.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23370: --------------------------------------- {quote} BTW, nowhere in this JIRA does it even state the new version of RedDeer you want to include. Details! {quote} {quote} We will want to update RedDeer in the TP to include the latest from [master] [..] I will simply create a snapshot with the rsync script and then give you the url. {quote} Isn't that enough? ;) OK, I will get you a URL later this week. And probably also provide PR for the target file. > Update RedDeer in TP for JBT 4.4.2.AM3 > -------------------------------------- > > Key: JBIDE-23370 > URL: https://issues.jboss.org/browse/JBIDE-23370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. > We will want to update RedDeer in the TP to include the latest from > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. > So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22628. ------------------------------------ verified in Devstudio 10.2.0.AM2-v20161017-1656-B6217 > Zoom in / out functionality is not working with Visual Page Editor > -------------------------------------------------------------------- > > Key: JBIDE-22628 > URL: https://issues.jboss.org/browse/JBIDE-22628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core > Affects Versions: 4.4.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.2.AM2 > > > New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-13661. ------------------------------------ verified in Devstudio 10.2.0.AM2-v20161017-1656-B6217 > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23066) Generating hbm.xml files always happens using the 3.5 runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23066?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23066: ------------------------------ Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Generating hbm.xml files always happens using the 3.5 runtime > ------------------------------------------------------------- > > Key: JBIDE-23066 > URL: https://issues.jboss.org/browse/JBIDE-23066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM3 > > > This issue is related to JBIDE-22997 and JBIDE-23059. After implementing JBIDE-23059 the phenomenon described in JBIDE-22997 disappeared but the hbm.xml files are now always generated using the 3.5 runtime, even when the project is a hibernate project with a console configuration using another version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016