October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-920) Create model editor actions test script

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-920?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-920: ----------------------------------------- [~mmajerni], in the future please prefer update an existing PR (just use {{push -f}}) instead of creating the new one. > Create model editor actions test script > --------------------------------------- > > Key: JBTIS-920 > URL: https://issues.jboss.org/browse/JBTIS-920 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.2.Final > Reporter: Mario Majernik > Assignee: Mario Majernik > Fix For: 4.3.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-920) Create model editor actions test script

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/JBTIS-920?page=com.atlassian.jira.plugin.... ] Mario Majernik updated JBTIS-920: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/811 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/810) > Create model editor actions test script > --------------------------------------- > > Key: JBTIS-920 > URL: https://issues.jboss.org/browse/JBTIS-920 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.2.Final > Reporter: Mario Majernik > Assignee: Mario Majernik > Fix For: 4.3.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23142) [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23142?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23142. --------------------------------- Assignee: Rob Stryker I tried this in devstudio 10.2.0.AM1 B6096. 1. I set up a cdk server normally. Make sure it works. 2. Quit devstudio 3. Make a new PATH entry in Windows for c:\HashiCorp-test\vagrant\bin in addition to c:\HashiCorp\vagrant\bin 4. Rename c:\HashiCorp to c:\HashiCorp-test 5. Reboot (for the new PATH entry to take effect) 6. Start devstudio 7. Open cdk server editor to see what happens This took a bit longer and the eclipse window even showed Not responding, so I was worried for a moment. But eventually it opened and when I checked launch config, it contained the new path. So I was happily surprised. I was then able to start cdk ok. It seems that some magic was happening when I was opening the server editor. So I wondered what would happen if I didn't open it and just tried to start cdk. So I carried on with the following: 8. Stop cdk, close cdk server editor and quit devstudio 9. Rename c:\HashiCorp-test back to c:\HashiCorp 10. Start devstudio 11. Launch cdk without opening the server editor first It still launched just fine. Then I carried on: 12. Stop cdk 13. Open cdk server editor 14. Open launch config And voila, the path to vagrant was already correct again. I still haven't verified the usecase when vagrant can't be located at all. So here's what I did: 15. Quit devstudio 16. Rename c:\HashiCorp to c:\HashiCorp-bla which is not on PATH 17. Start devstudio 18. Open cdk server editor + launch config I now get a warning that vagrant cannot be located. 19. Point the config to your new vagrant location 20. Start cdk It still works. So I'm quite happy that all the use cases seem to work. Closing. > [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-23142 > URL: https://issues.jboss.org/browse/JBIDE-23142 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > Steps to replicate: > 1) Create a new cdk server adapter on windows > 2) Open launch configuration and find the vagrant location > 3) Move that vagrant to another folder which is also on path > 4) Re-open launch config, note the launch config errors, and you cannot change it > Ideally, it will locate the new vagrant location. If not, it should allow you to set the new vagrant location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23312) When an OS certificate is accepted, the preference is not always saved

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23312?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23312: --------------------------------------- Unfortunately I am not able to reproduce. Do you have reliable steps to reproduce? > When an OS certificate is accepted, the preference is not always saved > ---------------------------------------------------------------------- > > Key: JBIDE-23312 > URL: https://issues.jboss.org/browse/JBIDE-23312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, preferences > Fix For: 4.4.2.AM3 > > > EXEC: clean up Openshift V3 SSL certificates > EXEC: connect to Openshift > ASSERT: the certificate dialog should pop up > EXEC:accept the cerificate and select remember > EXEC: stop Eclipse > EXEC: start Eclipse > EXEC: connect to Openshift > ASSERT: the certificate dialog popups again -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23313) OpenShift Connection: Accept SSL certificate shell is shown many times if I refresh a connection with not yet accepted cert

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23313?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23313: ---------------------------------- Labels: connection openshift_v3 (was: ) > OpenShift Connection: Accept SSL certificate shell is shown many times if I refresh a connection with not yet accepted cert > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23313 > URL: https://issues.jboss.org/browse/JBIDE-23313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: connection, openshift_v3 > > If I have a running IDE and remove SSL certificate in OS3 preference page for an existing OpenShift connection and then I click Refresh in context menu of the connection, Untrested SSL Certificate shell is shown 22 times. Precisely 22 new Untrested SSL Certificate shells are opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23313) OpenShift Connection: Accept SSL certificate shell is shown many times if I refresh a connection with not yet accepted cert

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23313: ------------------------------------- Summary: OpenShift Connection: Accept SSL certificate shell is shown many times if I refresh a connection with not yet accepted cert Key: JBIDE-23313 URL: https://issues.jboss.org/browse/JBIDE-23313 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM1 Reporter: Marián Labuda If I have a running IDE and remove SSL certificate in OS3 preference page for an existing OpenShift connection and then I click Refresh in context menu of the connection, Untrested SSL Certificate shell is shown 22 times. Precisely 22 new Untrested SSL Certificate shells are opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23193) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Base]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23193?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23193. --------------------------------- > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Base] > -------------------------------------------------------------- > > Key: JBIDE-23193 > URL: https://issues.jboss.org/browse/JBIDE-23193 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, usage > Reporter: Friendly Jira Robot > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Base]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) create rh-eclipse46-devstudio rpm for linux installs

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3982. ------------------------------- Closing. > create rh-eclipse46-devstudio rpm for linux installs > ---------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20341) Unable to deselect all items in JavaScript/Modules

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20341?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20341. ------------------------------ Verified in 10.2.0.AM2 build. > Unable to deselect all items in JavaScript/Modules > -------------------------------------------------- > > Key: JBIDE-20341 > URL: https://issues.jboss.org/browse/JBIDE-20341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2-v20150717-1420-B67, AngularJS installed from JBoss Central > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.4.1.Final > > > 1. Create new JavaScript project > 2. Open Properties > JavaScript > Modules for this project deselect all modules and click OK to close dialog > 3. Reopen Properties dialog > ERROR: AngularJS, Browser, Completion Guess and ECMAScript modules are checked and code assist offers items from these modules -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23312) When an OS certificate is accepted, the preference is not always saved

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23312: ---------------------------------- Summary: When an OS certificate is accepted, the preference is not always saved Key: JBIDE-23312 URL: https://issues.jboss.org/browse/JBIDE-23312 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM1 Reporter: Jeff MAURY Fix For: 4.4.2.AM3 EXEC: clean up Openshift V3 SSL certificates EXEC: connect to Openshift ASSERT: the certificate dialog should pop up EXEC:accept the cerificate and select remember EXEC: stop Eclipse EXEC: start Eclipse EXEC: connect to Openshift ASSERT: the certificate dialog popups again -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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