September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4048: -------------------------------- Sprint: devex #122 October 2016 > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4048: -------------------------------- Sprint: (was: devex #122 October 2016) > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4048: -------------------------------- Sprint: (was: devex #121 September 2016) > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ embed call to ./util/createTaskJIRAs.py inside ./util/getProjectRootPomParents.sh > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ Can now call createTaskJIRAs for a single JBIDE or JBDS issue: {code} python createTaskJIRAs.py -s https://issues.stage.jboss.org -u USR -p PWD --jbide 4.4.2.AM2 --jbds 10.2.0.AM2 --task "test for JBIDE-23091" -c foundation --jiraonly python createTaskJIRAs.py -s https://issues.stage.jboss.org -u USR -p PWD --jbide 4.4.2.AM2 --jbds 10.2.0.AM2 --task "test for JBIDE-23091" -c server --jiraonly python createTaskJIRAs.py -s https://issues.stage.jboss.org -u USR -p PWD --jbide 4.4.2.AM2 --jbds 10.2.0.AM2 --task "test for JBIDE-23091" -c openshift --jiraonly ... python createTaskJIRAs.py -s https://issues.stage.jboss.org -u USR -p PWD --jbide 4.4.2.AM2 --jbds 10.2.0.AM2 --task "test for JBIDE-23091" -C installer --jiraonly {code} And each call will simply return the JIRA ID of the created issue, eg., JBIDE-22768 or JBDS-3946, so the call can be wrapped by a shell script. > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be packed jars not unpacked directories for efficiency sake

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-3628: --------------------------------- Fix Version/s: (was: 4.3.x) > Plugins should be packed jars not unpacked directories for efficiency sake > -------------------------------------------------------------------------- > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common, hibernate, jsf, visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. Help content that is stored in zip files should be unpacked > 6. TBD -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23184: ------------------------------------- Description: Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 was: Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM2 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23150: ------------------------------------------ it's not a bug connected with Opeshift Explorer view. I would say that it is not a bug at all, but an intended behavior of the Properties view. For example, try the same trick you described, but with, say, Git Repositories view. It works the same way. [Here is the description|https://eclipse.org/articles/Article-WorkbenchSelections/arti...] of the mechanism of Selection Service. The thing we need is in the beginning of The Big Picture chapter: {panel:title=The Big Picture} Each workbench window has its own selection service instance. _The service keeps track of the selection in *the currently active part*_ and propagates selection changes to all registered listeners. Such selection events occur when the selection in the current part is changed or when a different part is activated. {panel} I want to say that when view X is in the same visual container with Properties view, and Properties view is active, X view can't be active and that's why can't be "parsed" on Properties. It's even more interesting - when Properties view is active, it is listened by selection service (according to the quote from the article above) and passes the data to the ... Properties view =) So Properties view displays the properties of the Properties view =) [~adietish], I would close this issue as not a bug > Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23150 > URL: https://issues.jboss.org/browse/JBIDE-23150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM2 > > Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png > > > If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot: > !openshift-explorer-and-properties-both-stacked.png! > and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty. > steps to reproduce: > # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container > # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse > # EXEC: make Properties view visible > # EXEC: make OpenShift explorer visible. Select an entry > # EXEC: switch back to Properties view > Result: > Properties view stays empty. You can switch back and forth, you wont get any content in the properties view. > !properties-empty.png! > Only moving Properties view to a different (visual) container helps. > the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Victor Rubezhny resolved JBIDE-21198. ------------------------------------- Resolution: Done > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.1.Final > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-21198: ------------------------------------ Fix Version/s: (was: 4.4.x) > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.1.Final > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- 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 September 2016