July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-3298. ------------------------------- Verified in JBDS 9.0.0.Beta2 respin-b. > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20236) Batch New and Noteworthy for 4.3.0.Beta2

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20236?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20236. ----------------------------------- Verified the N&N. Note: the mentioned Jira was not fixed in beta2 but moved to cr1. > Batch New and Noteworthy for 4.3.0.Beta2 > ---------------------------------------- > > Key: JBIDE-20236 > URL: https://issues.jboss.org/browse/JBIDE-20236 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Batch is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Batch by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17207) Run tests on all major OS

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17207. -------------------------------- Task done. Closing. > Run tests on all major OS > ------------------------- > > Key: JBIDE-17207 > URL: https://issues.jboss.org/browse/JBIDE-17207 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac. > For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200. > We don't have to run them every day. Maybe once a week or month? > cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server without runtime in JMX Navigator

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19463. --------------------------------- Verified in JBDS 9.0.0.Beta2 B93 > Cannot connect to remote server without runtime in JMX Navigator > ---------------------------------------------------------------- > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: jmx-text.png > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20114) New server uses openshift.redhat.com host name in case OpenShift server adapter has been selected in tree

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20114?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20114. --------------------------------- I'm really not entirely sure which is better - the previous behavior or the new one. Perhaps now it will annoy less people. Hopefully. Verified in JBDS 9.0.0.Beta2 B93 > New server uses openshift.redhat.com host name in case OpenShift server adapter has been selected in tree > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20114 > URL: https://issues.jboss.org/browse/JBIDE-20114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.Beta2 > > > If in New server wizard in tree containing server types is selected at first OpenShift server adapter and then any server, host name stays openshift.redhat.com. If user is not careful enough, he does not have to notice this and his server won't start. Host name in wizard should change accordingly to used server (prefill localhost for servers). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20188) when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20188?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20188. --------------------------------- Verified in JBDS 9.0.0.Beta2 B93 > when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse > ------------------------------------------------------------------------------ > > Key: JBIDE-20188 > URL: https://issues.jboss.org/browse/JBIDE-20188 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.3.0.Beta1, 4.3.x > Reporter: Lars Heinemann > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > When you expand an entry in the JMX Navigator into a deeper level ( for instance java.lang -> Compilation ) and then invoke the context menu "Refresh" on that node (Compilation) it collapses the whole tree and you loose your selection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20317) 'Create JMX Connection' button from 'JMX Navigator' action bar creates extra window without content

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20317?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20317. --------------------------------- [~psrna] verified this for me on Linux (I saw it with my own eyes) with JBDS 9.0.0.Beta2 respin-b. The strange empty window is no longer appearing. Closing. > 'Create JMX Connection' button from 'JMX Navigator' action bar creates extra window without content > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-20317 > URL: https://issues.jboss.org/browse/JBIDE-20317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: screenshot1.png > > > Every time I push "Create JMX Connection" button in JMX Navigator it created wizard and empty window > !screenshot1.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3384. ------------------------------- Hey [~rob.stryker], it seems this is done. Is there any action item for QE to verify this? If you can think of any, please let us know. Closing for now. > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19963. ------------------------------ Verified in JBDS 9.0.0.Beta2 respin-b. Tern is in version 0.10.0.201506172157. > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy, respin-a > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19694. ------------------------------ Verified in JBDS 9.0.0.Beta2 respin-b. > Angular Explorer doesn't show anything > -------------------------------------- > > Key: JBIDE-19694 > URL: https://issues.jboss.org/browse/JBIDE-19694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Beta2 > > Attachments: empty-modules.png, filled-modules.png, screenshot_kitchensink-respinb.png, tern-java-revisions.png > > > # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source > # Checkout step-12 branch of imported project > # Open Angular Explorer > # Open index.html file of angular-phonecat project > ERROR: Angular Explorer is empty. It should contain angular controllers and modules > Was working fine with JBDS 8.1.0.GA and the same project configuration -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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