September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22225: ------------------------------------ {quote} when do we have Neon.1 in our TP?{quote} [~adietish] See https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedules ...once the bits are live (quiet week) I can start mirroring them and can then update our TP to include Neon.1. Might be able to start as early as this Friday Sep 16, if it's urgent (and there are no late respins from Eclipse.org). > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23140 at 9/12/16 9:55 AM: ------------------------------------------------------------- See below for what's installed on wonka [0], on which I can successfully build the rpmbuild/mock project. [0] wonka.mw.lab.eng.bos.redhat.com (10.16.89.81) You probably don't need ALL of that, but it should give you a good idea of what's needed. The script [1], for the build we'd like to run on a RHEL7 slave (w/ mock and rpmbuild installed) in central-ci, also lists a few requirements: {code} su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.no...' su -c 'yum install mock' su -c 'yum install rpm-build redhat-rpm-config' su -c '$(which usermod) -a -G mock $USER' su -c 'cp rh-eclipse46.repo /etc/yum.repos.d/rh-eclipse46.repo' su -c 'yum install eclipse-platform' {code} [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build.sh The file rh-eclipse46.repo (as used in the scriplet above) is here [2]. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/rh-ecl... was (Author: nickboldt): Here's what's installed on wonka [0], on which I can successfully build the rpmbuild/mock project: [^yum.install.list.txt] [0] wonka.mw.lab.eng.bos.redhat.com (10.16.89.81) You don't need ALL of that, but it should give you a good idea of what's needed. The script [1], for the build we'd like to run on a RHEL7 slave (w/ mock and rpmbuild installed) in central-ci, also lists a few requirements: {code} su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.no...' su -c 'yum install mock' su -c 'yum install rpm-build redhat-rpm-config' su -c '$(which usermod) -a -G mock $USER' su -c 'cp rh-eclipse46.repo /etc/yum.repos.d/rh-eclipse46.repo' su -c 'yum install eclipse-platform' {code} [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build.sh The file rh-eclipse46.repo (as used in the scriplet above) is here [2]. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/rh-ecl... > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.x > > Attachments: yum.install.list.partial.txt, yum.install.list.sort.txt, yum.install.list.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23140: ------------------------------- Attachment: yum.install.list.txt yum.install.list.sort.txt yum.install.list.partial.txt Here's a simple (partial?) list of installed rpms: {code} cat /var/log/yum.log | sed "s#.\+: \?$.\+$#\1#" | egrep -v rh-eclipse | sort > yum.install.list.txt {code} -- [^yum.install.list.partial.txt] Or, for a more complete list of installed rpms: {code} for id in {1..48}; do yum history info $id | egrep "Installed|Updated" | tee -a /tmp/yum.install.list.txt; done{code} -- [^yum.install.list.txt] {code} cat /tmp/yum.install.list.txt | sort | uniq | sed -e "s#.\+[\ \t]\+$[a-zA-Z].\+\\(noarch\|64\|6$\).\+\@.\+#\1#" | sort | tee /tmp/yum.install.list.sort.txt{code} -- [^yum.install.list.sort.txt] > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.x > > Attachments: yum.install.list.partial.txt, yum.install.list.sort.txt, yum.install.list.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23140: ------------------------------- Attachment: (was: yum.install.list.txt) > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x

by Antal Varga (JIRA)

Antal Varga created JBIDE-23149: ----------------------------------- Summary: Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x Key: JBIDE-23149 URL: https://issues.jboss.org/browse/JBIDE-23149 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.4.0.Final Reporter: Antal Varga The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later. private Object newReverseEngineeringStrategy(String className, Object delegate) {...} tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*. The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught). Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated). *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23140 at 9/12/16 9:32 AM: ------------------------------------------------------------- Here's what's installed on wonka [0], on which I can successfully build the rpmbuild/mock project: [^yum.install.list.txt] [0] wonka.mw.lab.eng.bos.redhat.com (10.16.89.81) You don't need ALL of that, but it should give you a good idea of what's needed. The script [1], for the build we'd like to run on a RHEL7 slave (w/ mock and rpmbuild installed) in central-ci, also lists a few requirements: {code} su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.no...' su -c 'yum install mock' su -c 'yum install rpm-build redhat-rpm-config' su -c '$(which usermod) -a -G mock $USER' su -c 'cp rh-eclipse46.repo /etc/yum.repos.d/rh-eclipse46.repo' su -c 'yum install eclipse-platform' {code} [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build.sh The file rh-eclipse46.repo (as used in the scriplet above) is here [2]. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/rh-ecl... was (Author: nickboldt): Here's what's installed on wonka [0], on which I can successfully build the rpmbuild/mock project: [^yum.install.list.txt] [0] wonka.mw.lab.eng.bos.redhat.com (10.16.89.81) You don't need ALL of that, but it should give you a good idea of what's needed. The script [1] also lists a few requirements: {code} su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.no...' su -c 'yum install mock' su -c 'yum install rpm-build redhat-rpm-config' su -c '$(which usermod) -a -G mock $USER' su -c 'cp rh-eclipse46.repo /etc/yum.repos.d/rh-eclipse46.repo' su -c 'yum install eclipse-platform' {code} [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build.sh The file rh-eclipse46.repo (as used in the scriplet above) is here [2]. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/rh-ecl... > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.x > > Attachments: yum.install.list.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23140: ------------------------------- Attachment: yum.install.list.txt Here's what's installed on wonka [0], on which I can successfully build the rpmbuild/mock project: [^yum.install.list.txt] [0] wonka.mw.lab.eng.bos.redhat.com (10.16.89.81) You don't need ALL of that, but it should give you a good idea of what's needed. The script [1] also lists a few requirements: {code} su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.no...' su -c 'yum install mock' su -c 'yum install rpm-build redhat-rpm-config' su -c '$(which usermod) -a -G mock $USER' su -c 'cp rh-eclipse46.repo /etc/yum.repos.d/rh-eclipse46.repo' su -c 'yum install eclipse-platform' {code} [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build.sh The file rh-eclipse46.repo (as used in the scriplet above) is here [2]. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/rh-ecl... > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.x > > Attachments: yum.install.list.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-880) Update known issues

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-880: --------------------------------- Summary: Update known issues Key: JBTIS-880 URL: https://issues.jboss.org/browse/JBTIS-880 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: BPMN2, QE Affects Versions: 9.0.2.CR1 Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23015 at 9/12/16 8:57 AM: ------------------------------------------------------------------- [#207|https://github.com/openshift/openshift-restclient-java/pull/207] was merged to openshift-restclient-java/master openshift-restclient-java 5.2.0-SNAPSHOT was deployed to nexus was (Author: adietish): [#207|https://github.com/openshift/openshift-restclient-java/pull/207] was merged to openshift-restclient-java/master > Creating a route should have a default port > ------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM1 > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23015 at 9/12/16 8:55 AM: ------------------------------------------------------------------- [#207|https://github.com/openshift/openshift-restclient-java/pull/207] was merged to openshift-restclient-java/master was (Author: adietish): https://github.com/openshift/openshift-restclient-java/pull/207 was merged to openshift-restclient-java/master > Creating a route should have a default port > ------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM1 > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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