April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19591) Explorer: connection is not refreshed if I edit it and change the host

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19591?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19591: ------------------------------------------ postponing this non-ciritical issue to 4.3.0.Beta1 > Explorer: connection is not refreshed if I edit it and change the host > ---------------------------------------------------------------------- > > Key: JBIDE-19591 > URL: https://issues.jboss.org/browse/JBIDE-19591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3406) JBDS doesn't prompt for workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3406?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3406: -------------------------------------- Same thing on Linux. Passing "-data <path>" to jbdevstudio launcher works, but no selection pop-up by default > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBDS-3406 > URL: https://issues.jboss.org/browse/JBDS-3406 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Fix For: 9.0.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19591) Explorer: connection is not refreshed if I edit it and change the host

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19591?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19591: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: connection is not refreshed if I edit it and change the host > ---------------------------------------------------------------------- > > Key: JBIDE-19591 > URL: https://issues.jboss.org/browse/JBIDE-19591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19338: --------------------------------------- [~vpakan], could you provide more details? May be you can do screen cast (video) of what you have tried? > Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19338 > URL: https://issues.jboss.org/browse/JBIDE-19338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Check the button "Show only palette groups for which libraries are defined on the page" > ASSERT: No Palette groups are visible in HTML 5 Palette > 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 4. Check the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed > 5. Uncheck the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19338: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19338 > URL: https://issues.jboss.org/browse/JBIDE-19338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Check the button "Show only palette groups for which libraries are defined on the page" > ASSERT: No Palette groups are visible in HTML 5 Palette > 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 4. Check the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed > 5. Uncheck the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19623) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19623?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-19623. --------------------------------- Resolution: Done > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Arquillian] > --------------------------------------------------------- > > Key: JBIDE-19623 > URL: https://issues.jboss.org/browse/JBIDE-19623 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [Arquillian]: 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.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|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.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {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 Arquillian 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)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3412) For JBDS 9.0.0.Alpha2: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3412?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3412. ---------------------------- Assignee: Nick Boldt Resolution: Done > For JBDS 9.0.0.Alpha2: Code Freeze + Branch > ------------------------------------------- > > Key: JBDS-3412 > URL: https://issues.jboss.org/browse/JBDS-3412 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 9.0.0.Alpha2 > > > For JBDS 9.0.0.Alpha2: 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.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|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.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {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...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19338: --------------------------------------- I tried jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar. But I needed to install "JBoss Tools Java Standard Tools AngularJS" from update site https://devstudio.redhat.com/updates/9.0.0/jboss-devstudio-9.0.0.Alpha1-u... Everything works just fine. > Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19338 > URL: https://issues.jboss.org/browse/JBIDE-19338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha2 > > > 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Check the button "Show only palette groups for which libraries are defined on the page" > ASSERT: No Palette groups are visible in HTML 5 Palette > 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 4. Check the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed > 5. Uncheck the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19584) Explorer: exception for v3 connection is has "New" context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19584?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19584: ------------------------------------------ postponing this non-ciritical issue to 4.3.0.Beta1 > Explorer: exception for v3 connection is has "New" context menu > --------------------------------------------------------------- > > Key: JBIDE-19584 > URL: https://issues.jboss.org/browse/JBIDE-19584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.3.0.Beta1 > > Attachments: new-context-menu-for-exception.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19584) Explorer: exception for v3 connection is has "New" context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19584?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19584: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: exception for v3 connection is has "New" context menu > --------------------------------------------------------------- > > Key: JBIDE-19584 > URL: https://issues.jboss.org/browse/JBIDE-19584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.3.0.Beta1 > > Attachments: new-context-menu-for-exception.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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