June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19976) Search for quickstarts in Central is not consistent

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-19976: ---------------------------------- Summary: Search for quickstarts in Central is not consistent Key: JBIDE-19976 URL: https://issues.jboss.org/browse/JBIDE-19976 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Beta1 Environment: Windows 8.1, Fedora 22 Reporter: Radim Hopp Most of the time, the the results provided by search do not have labels. Once Central is opened, it returns the same results, but sometimes when you close&reopen central it cannot find quickstarts it could found previously and vice versa. For example right now, I have two instances of JBT/JBDS openew with central and searching for "greeter" in one results in no quickstarts found and in the second one finds just one quickstart - "jboss-greeter". After closing and reopening Central in the instance, which previously has shown "jboss-greeter", when seached for "greeter", now it finds some another quickstart named "greeter". I couldn't find any determinism in this behaviour. I can see no errors in error log, nor any error dialog. Sometimes, when I click on the found quickstart, new quickstart wizard is shown, sometimes nothing happens (again, no error anywhere). I have tried it on JBT 4.3.0.Beta1 on Fedora 22 with GTK3/GTK2, JBDS 9.0.0.Beta1 on Fedora 22 with GTK2/3 and on Windows 8.1 on JBDS 9.0.0.Beta1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19975: ------------------------------------- Attachment: edit-template-parameter-value.png required-value-decoration.png > v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19975 > URL: https://issues.jboss.org/browse/JBIDE-19975 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: 4.3.0.Beta2 > > Attachments: edit-template-parameter-value.png, required-value-decoration.png > > > # ASSERT: make sure that you have a connection to a v3 OpenShift server > # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection > # ASSERT: new application wizard pops up, listing your project > # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next" > # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit" > # ASSERT: editing dialog pops up > Result: > !edit-template-parameter-value.png! > "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value? > # EXEC: provide some value and back in the wizard page hit "Next" > # ASSERT: "Resource Labels" page shows up. > # EXEC: Hit "Add" > # ASSERT: dialog pops up so that I can create a new label > Result: > !required-value-decoration.png! > The dialog decorates missing values with a red error marker > !required-value-decoration.png! > In OpenShift tooling we usually use "*" when required values are missing, not the error icon. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3300) include EAP 6.4 in JBDS installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3300?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3300. ----------------------------- Verified for 9.0.0.Beta1, closing. > include EAP 6.4 in JBDS installer > --------------------------------- > > Key: JBDS-3300 > URL: https://issues.jboss.org/browse/JBDS-3300 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: installer > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Include EAP 6.4 (or an early Alpha/Beta/CR?) in JBDS 9 installer, once it's available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3445) Request users to choose java 8 or higher when installing JBDS 9

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3445?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3445. ----------------------------- Verified for 9.0.0.Beta1, closing. > Request users to choose java 8 or higher when installing JBDS 9 > --------------------------------------------------------------- > > Key: JBDS-3445 > URL: https://issues.jboss.org/browse/JBDS-3445 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Based on the decision on JBDS PM call today, we will only support JBDS to be running on Java 8 or higher in 9.0.0.Beta1. So the installer shouldn't let users choose java 7 for the installation. > Just to be clear: The installer itself will still work fine with java 6 or 7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19947: ------------------------------- Attachment: JDK7-warning.png When I first installed Eclipse & then installed JBDS 4.3.0.Beta1, then ran Eclipse with JDK 7, I got this warning: !JDK7-warning.png! But not sure if there's a way to PREVENT users from updating. Better would be to maybe change the license text to something that would appear in their face at update time, like: "WARNING: This update will require you to ALSO switch to using JDK 8, as JDK 7 can no longer be used to run JBoss Tools or Red Hat JBoss Developer Studio." We could add this to the license for the feature that includes foundation.core and Arquillian, plus any other features which have plugins which set a BREE = JavaSE-1.8. > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Attachments: error1.jpg, error2.jpg, error3.jpg, JDK7-warning.png > > > Description of problem: > After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > Jdk: 1.7 > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) Template label decorators don't go away

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19952?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19952: ------------------------------------- Attachment: additional-error-marker.png > Template label decorators don't go away > --------------------------------------- > > Key: JBIDE-19952 > URL: https://issues.jboss.org/browse/JBIDE-19952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Attachments: additional-error-marker.png, Resource Label dialog.png > > > While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. > Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19951: --------------------------------------- [~nickboldt], sorry, but I don't understand. We upversioned from 4.2.0 (used in 4.2.x branch) to 4.3.0 some time ago. So now both master and 4.3.0.Beta1x branch contain version 4.3.0, that should be fine, no? > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests] > --------------------------------------------------------------- > > Key: JBIDE-19951 > URL: https://issues.jboss.org/browse/JBIDE-19951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 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.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) Template label decorators don't go away

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19952?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19952: ------------------------------------------ I cant reproduce this as shown above. I have a slightly different behaviour which I assume is caused by redraw problems. !additional-error-marker.png! I have an additional error-marker in the left lower corner of the text-field for the label. All error-decorations but that one go away once I provide content. The additional error marker goes away once the editing-dialog looses the focus. > Template label decorators don't go away > --------------------------------------- > > Key: JBIDE-19952 > URL: https://issues.jboss.org/browse/JBIDE-19952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Attachments: Resource Label dialog.png > > > While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. > Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19975: ---------------------------------------- Summary: v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling Key: JBIDE-19975 URL: https://issues.jboss.org/browse/JBIDE-19975 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19975: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19975 > URL: https://issues.jboss.org/browse/JBIDE-19975 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015