September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23152: ---------------------------------- Summary: NPE when deploying image with ENV with no value Key: JBIDE-23152 URL: https://issues.jboss.org/browse/JBIDE-23152 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.Final Reporter: Jeff MAURY Fix For: 4.4.2.AM2 EXEC: first deploy jboss-eap64-openshift ASSERT: wait until deployment is finished EXEC: delete the deployment EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd) ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23106) OpenShift New and Noteworthy for 4.4.1.Final

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23106?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23106. --------------------------------- > OpenShift New and Noteworthy for 4.4.1.Final > -------------------------------------------- > > Key: JBIDE-23106 > URL: https://issues.jboss.org/browse/JBIDE-23106 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > 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...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor/focus

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-23132: --------------------------------------- I have opened just one ftl, so the difference is not there. When the editor doesn't get focused, what happens if you click into the text with the mouse? Nothing? How do you try to open the context assistant that times out? > When ftl file is opened in devstudio/eclipse it does not get cursor/focus > ------------------------------------------------------------------------- > > Key: JBIDE-23132 > URL: https://issues.jboss.org/browse/JBIDE-23132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.Final > Environment: Fedora 24, x86_64, devstudio: > Version: 10.1.0.GA > Build id: GA-v20160902-1725-B43 > Eclipse neon 1, RC1 > Reporter: Ondrej Dockal > Assignee: Daniel Dekany > > When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements jboss tools team did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23127: ---------------------------------------- Thanks Jeff, I'll add a link to this N&N and a few words about the main additions. > blog about the improvements jboss tools team did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > Topics for Neon: > * SWT > * Docker and Vagrant Tools > * JSDT & JS package > * Ctrl+/- on text > * Importer > * Disabling theming > Topics for Oxygen > * Generic editor > * language server > * ,,, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22375: ----------------------------------- Assignee: (was: Fred Bricon) > Improve HCR OpenShift > --------------------- > > Key: JBIDE-22375 > URL: https://issues.jboss.org/browse/JBIDE-22375 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Priority: Blocker > Fix For: 4.4.x > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22860: ----------------------------------- Assignee: (was: Fred Bricon) > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements jboss tools team did to Neon

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Jeff Johnston edited comment on JBIDE-23127 at 9/12/16 6:54 PM: ---------------------------------------------------------------- Have you looked at our N&N for our Neon.1 5.1.0 release: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 or are you just interested in Neon.0? was (Author: jjohnstn): Have you looked at our N&N for our Neon.1 5.1.0 release: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > blog about the improvements jboss tools team did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > Topics for Neon: > * SWT > * Docker and Vagrant Tools > * JSDT & JS package > * Ctrl+/- on text > * Importer > * Disabling theming > Topics for Oxygen > * Generic editor > * language server > * ,,, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements jboss tools team did to Neon

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-23127: --------------------------------------- Have you looked at our N&N for our Neon.1 5.1.0 release: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > blog about the improvements jboss tools team did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > Topics for Neon: > * SWT > * Docker and Vagrant Tools > * JSDT & JS package > * Ctrl+/- on text > * Importer > * Disabling theming > Topics for Oxygen > * Generic editor > * language server > * ,,, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20904: ------------------------------------ Initial attempt at wrapping a job around the release steps for jbt/ds blocked by problems w/ ssh/rsync/sftp: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-d... https://engineering.redhat.com/rt/Ticket/Display.html?id=419583 > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20904: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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