February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19162: --------------------------------------------- [~nickboldt] openshift v2 and v3 shares 90% of UI/functionality. It does *not* make sense introducing a different connector for this. We have a *single* openshift proxy wizard and when it is chosen (and you do not already have OS installed) on devstudio you will be asked to install openshift v2, in tools you will be suggested to install OpenShift v2 AND OpenShift v3 support and you can choose either. This matches perfectly with what we are doing here: adding early version of of V3 to JBoss Tools in additon to v2 and for devstudio we stay with just v2. > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19257) Openshift v2 connections do not load from preferences

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19257: ------------------------------------- Summary: Openshift v2 connections do not load from preferences Key: JBIDE-19257 URL: https://issues.jboss.org/browse/JBIDE-19257 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19235) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19235?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19235: ------------------------------------------ done > For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift] > -------------------------------------------------------- > > Key: JBIDE-19235 > URL: https://issues.jboss.org/browse/JBIDE-19235 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [OpenShift]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha1x > git push origin jbosstools-4.3.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19235) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19235?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19235. ------------------------------------ Assignee: Andre Dietisheim Resolution: Done > For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift] > -------------------------------------------------------- > > Key: JBIDE-19235 > URL: https://issues.jboss.org/browse/JBIDE-19235 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [OpenShift]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha1x > git push origin jbosstools-4.3.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19256?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19256: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.3.Beta1) > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-19256 > URL: https://issues.jboss.org/browse/JBIDE-19256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19256?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19256: ---------------------------------------- The issue has been fixed upstream - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444143 > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-19256 > URL: https://issues.jboss.org/browse/JBIDE-19256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19256?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-19256. ------------------------------------ Resolution: Done > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-19256 > URL: https://issues.jboss.org/browse/JBIDE-19256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18755) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18755?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18755: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.3.0.Alpha2) > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-18755 > URL: https://issues.jboss.org/browse/JBIDE-18755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Karel Piwko > Fix For: 4.2.3.Beta1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18755) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18755?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18755: -------------------------------------- Assignee: Alexey Kazakov > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-18755 > URL: https://issues.jboss.org/browse/JBIDE-18755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Karel Piwko > Assignee: Alexey Kazakov > Fix For: 4.2.3.Beta1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19256: -------------------------------------- Summary: Autocomplete shows white on white using default RHEL7 theme Key: JBIDE-19256 URL: https://issues.jboss.org/browse/JBIDE-19256 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Affects Versions: 4.2.0.Final Environment: JBDS 8.0.0, RHEL 7 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.3.Beta1 I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015