November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22138: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Fred Bricon > Labels: openshift_v3, server_adapter > Fix For: 4.4.x > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22138: ------------------------------------- Summary: Server adapter: doesn't respect openshift maven profile (was: Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile) > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Fred Bricon > Fix For: 4.4.x > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4146: ---------------------------------- So, the issue here is that when rh-eclipse46-eclipse-epp-logging-2.0.3-1.1.el7.noarch and/or eclipse-epp-logging-2.0.3-1.fc24.noarch are built, someone changed the MANIFEST.MF files to include the latest lucene 5.4.1 instead of 3.5.0. > Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4146 > URL: https://issues.jboss.org/browse/JBDS-4146 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Minor > Fix For: 10.x > > Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, eclipse-log-after-new-workspace.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt > > > As of the latest rpm build [1] I'm only getting this one error now: > {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075 > !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629 > !STACK 0 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4172) Add eGit git flow plugin to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4172?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4172: ---------------------------------- Would you also want this added to JBoss Tools? Would it be an optional install via Central, or an OOTB install as part of some other feature (eg., openshift or com.jboss.devstudio.core) ? > Add eGit git flow plugin to devstudio > ------------------------------------- > > Key: JBDS-4172 > URL: https://issues.jboss.org/browse/JBDS-4172 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 10.2.0.AM3 > Reporter: Radim Hopp > Assignee: Alexey Kazakov > Fix For: 10.x > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4172) Add eGit git flow plugin to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4172?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4172: -------------------------------- Assignee: Alexey Kazakov > Add eGit git flow plugin to devstudio > ------------------------------------- > > Key: JBDS-4172 > URL: https://issues.jboss.org/browse/JBDS-4172 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 10.2.0.AM3 > Reporter: Radim Hopp > Assignee: Alexey Kazakov > Fix For: 10.x > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4172) Add eGit git flow plugin to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4172?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4172: ----------------------------- Fix Version/s: 10.x > Add eGit git flow plugin to devstudio > ------------------------------------- > > Key: JBDS-4172 > URL: https://issues.jboss.org/browse/JBDS-4172 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 10.2.0.AM3 > Reporter: Radim Hopp > Assignee: Alexey Kazakov > Fix For: 10.x > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23478) Central is missing scrollbar when it's too small

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-23478: ---------------------------------- Summary: Central is missing scrollbar when it's too small Key: JBIDE-23478 URL: https://issues.jboss.org/browse/JBIDE-23478 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.4.2.AM3 Environment: Devstudio 10.2.0.AM3 Reporter: Radim Hopp Assignee: Radim Hopp When central is shrinked too much, user cannot select examples, access pagination etc. It would be nice to add scrollbar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-3903. ------------------------------- New section about additional installation of Docker(in order to use full version of Docker) has been added in documentation. > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-23026 at 11/9/16 8:30 AM: ---------------------------------------------------------------- IT tests are not stable enough to have them passed in a single run, sometimes because of timeouts, other times bcs. of UI bugs. But there are also some issues I found recently and once I finish with current tasks, I am about to fix it and make it more stable and runnable on Central CI, probably on OpenShift from minishift. What are the most common issues? At the moment the most significant issue is https://issues.jboss.org/browse/JBIDE-23463 which break many tests bcs. we were waiting for a finished build pod and thus it is failing. was (Author: mlabuda): IT tests are not stable enough to have them passed in a single run, sometimes because of timeouts, other times bcs. of UI bugs. But there are also some issues I found recently and once I finish with current tasks, I am about to fix it and make it more stable and runnable on Central CI, probably on OpenShift from minishift. What are the most common issues? > Integration tests: improve test stability > ----------------------------------------- > > Key: JBIDE-23026 > URL: https://issues.jboss.org/browse/JBIDE-23026 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: integration_tests > Fix For: 4.4.2.Final > > > There are several impediments to the test stability: > * tests dont set up their env individually > * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-23026 at 11/9/16 8:28 AM: ---------------------------------------------------------------- IT tests are not stable enough to have them passed in a single run, sometimes because of timeouts, other times bcs. of UI bugs. But there are also some issues I found recently and once I finish with current tasks, I am about to fix it and make it more stable and runnable on Central CI, probably on OpenShift from minishift. What are the most common issues? was (Author: mlabuda): IT tests are not stable enough to have them passed in a single run, sometimes because of timeouts, other times bcs. of UI bugs. But there are also some issues I found recently and once I finish with current tasks, I am about to fix it and make it more stable and runnable on Central CI, probably on OpenShift from minishift. > Integration tests: improve test stability > ----------------------------------------- > > Key: JBIDE-23026 > URL: https://issues.jboss.org/browse/JBIDE-23026 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: integration_tests > Fix For: 4.4.2.Final > > > There are several impediments to the test stability: > * tests dont set up their env individually > * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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 November 2016