February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23603: ------------------------------------------ [~jeffmaury] [~dbocharov] I see us having merged this patch, that you're unhappy with. So this seems like a functional "workaround" that we will properly fix in a new jira for 4.4.4.AM1 or are there additional commits expected for this jira? We should either resolve this issue and create a followup jira or keep this opened until we have the additional changes merged in. > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23898) Link is not working in repository

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23898?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-23898: ---------------------------------- Priority: Minor (was: Major) > Link is not working in repository > --------------------------------- > > Key: JBIDE-23898 > URL: https://issues.jboss.org/browse/JBIDE-23898 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: rpm > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Minor > Attachments: rpm-repo-link.png > > > Hi, > the link "*Details here*" in repository for RPM (https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/) is not working. It is pointing to https://access.redhat.com/articles/4274103 but it gives error 404 - not found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23898) Link is not working in repository

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-23898: ------------------------------------- Summary: Link is not working in repository Key: JBIDE-23898 URL: https://issues.jboss.org/browse/JBIDE-23898 Project: Tools (JBoss Tools) Issue Type: Task Components: rpm Reporter: Josef Kopriva Attachments: rpm-repo-link.png Hi, the link "*Details here*" in repository for RPM (https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/) is not working. It is pointing to https://access.redhat.com/articles/4274103 but it gives error 404 - not found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23898) Link is not working in repository

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23898?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-23898: ------------------------------------- Assignee: Nick Boldt > Link is not working in repository > --------------------------------- > > Key: JBIDE-23898 > URL: https://issues.jboss.org/browse/JBIDE-23898 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: rpm > Reporter: Josef Kopriva > Assignee: Nick Boldt > Attachments: rpm-repo-link.png > > > Hi, > the link "*Details here*" in repository for RPM (https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/) is not working. It is pointing to https://access.redhat.com/articles/4274103 but it gives error 404 - not found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1043) Wrong version format in DevstudioIS features

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1043: ---------------------------------------- Summary: Wrong version format in DevstudioIS features Key: JBTIS-1043 URL: https://issues.jboss.org/browse/JBTIS-1043 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 10.1.0.GA Reporter: Andrej Podhradsky Priority: Blocker It is |com.jboss.devstudio.integration-stack.bpr.feature | 10.1.0.2017-02-14_19-25-v20170214-1949-B277| |com.jboss.devstudio.integration-stack.ds.feature | 10.1.0.2017-02-14_19-25-v20170214-1949-B277| |com.jboss.devstudio.integration-stack.fuse.feature | 10.1.0.2017-02-14_19-25-v20170214-1949-B277| |com.jboss.devstudio.integration-stack.soa.feature | 10.1.0.2017-02-14_19-25-v20170214-1949-B277| but should be {code} 10.1.0.GA-v20170214-1949-B277 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22362: ------------------------------------------ merged into master > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-4263: --------------------------------- A new build of Eclipse was done for RHSCL that contains Roland's feature groups patch. For the various singleton problems, please retry the test with rh-eclipse46-eclipse-platform >= 4.6.2-4.4 > Problems after install from Red Hat Central into rh-eclipse46-devstudio > ----------------------------------------------------------------------- > > Key: JBDS-4263 > URL: https://issues.jboss.org/browse/JBDS-4263 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 10.3.0.GA > > Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4265) Remove more jgit/egit bundles from devstudio rpm?

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4265?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4265. ------------------------------ Verified in Devstudio RPM 10.3-0.20170215.0300.el7. Egit works properly, no errors in the log. Closing. > Remove more jgit/egit bundles from devstudio rpm? > ------------------------------------------------- > > Key: JBDS-4265 > URL: https://issues.jboss.org/browse/JBDS-4265 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > > Mat asked, re: https://github.com/jbdevstudio/jbdevstudio-product/commit/15972aaaa17a4f8... : > {quote} > Hmm, Devstudio supplies jgit? > We also supply it as part of RHSCL in package rh-eclipse46-eclipse-jgit.noarch > {code}$ ls /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/jgit/eclipse/plugins > com.googlecode.javaewah.JavaEWAH_0.8.4.jar > com.google.gson_2.2.4.jar > org.apache.commons.compress_1.5.0.jar > org.eclipse.jgit_4.6.0.201612231935-r.jar > org.eclipse.jgit.archive_4.6.0.201612231935-r.jar > org.eclipse.jgit.http.apache_4.6.0.201612231935-r.jar > org.eclipse.jgit.http.server_4.6.0.201612231935-r.jar > org.eclipse.jgit.junit_4.6.0.201612231935-r.jar > org.eclipse.jgit.junit.http_4.6.0.201612231935-r.jar > org.eclipse.jgit.lfs_4.6.0.201612231935-r.jar > org.eclipse.jgit.lfs.server_4.6.0.201612231935-r.jar > org.eclipse.jgit.pgm_4.6.0.201612231935-r.jar > org.eclipse.jgit.ui_4.6.0.201612231935-r.jar > org.hamcrest.core_1.3.0.v201303031735.jar > org.junit_4.12.0.jar > org.kohsuke.args4j_2.32.0.jar > slf4j.api_1.7.4.jar > slf4j.simple_1.7.4.jar{code}{quote} > Devstudio REQUIRES jgit: > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu... > And we specifically blacklist a lot of egit and jgit bundles. Maybe we need to blacklist more? > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu... > If it's dragged in by stuff in Openshift or M2E, we'll have to get that fixed in upstream so it's only Import-Package'ing instead of Require-Bundle'ing. > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23817: ------------------------------------- Story Points: 4 > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23817: ------------------------------------------ merged into master > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017