September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22626: ------------------------------------------ [~jcantrill] i just don't understand then why doesn't it work as it is described in docs: _"With the above example, when *the latest tag value of the* origin-ruby-sample *image stream changes* and *the new image value differs from the current image* specified in the deployment configuration’s helloworld container, a new deployment is created using the new image for the helloworld container."_ I've changed the tag of the IS and the image value differes, why didn't a new deployment happen? > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: ImageStreamTags.jpg > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. > Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht... > Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22581: ------------------------------------ update neon, m2e-wtp, launchbar, wtp, docker > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM1 > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22362: -------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM2 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22628: -------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Zoom in / out functionality is not working with Visual Page Editor > -------------------------------------------------------------------- > > Key: JBIDE-22628 > URL: https://issues.jboss.org/browse/JBIDE-22628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core > Affects Versions: 4.4.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.4.2.AM2 > > > New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23128) Eclipse Neon.1 JSDT Blog

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23128?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-23128: -------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Eclipse Neon.1 JSDT Blog > ------------------------- > > Key: JBIDE-23128 > URL: https://issues.jboss.org/browse/JBIDE-23128 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, upstream, website > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.2.AM2 > > > Need to write blog about Neon.1 JSDT improvements. Tentative structure: > - Node.js Debugger improvements > - New JavaScript Debugger > - npm scripts support > - OMPH installer support > - Important bug fixes (provide a query with all Neon.1 bug fixes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22225: -------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23179) "poweroff" not recognized as a vagrant state in master

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23179?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23179: --------------------------------------- [~rob.stryker], can you explain the implications of this to me please? Does this mean that before, if vagrant status returned "not created", the tooling would not properly categorise this as stopped? So for example if you start cdk in eclipse, then "vagrant destroy" in cli and then stop in eclipse, it would not work before, but works now? (Indeed, it does work for me.) And one more question, you parse the vagrant status output here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... I don't fully understand exactly how you parse it. But I wonder, the constant is "not_created" whereas the vagrant status will return "not created" (with space). Is that taken into account? > "poweroff" not recognized as a vagrant state in master > ------------------------------------------------------ > > Key: JBIDE-23179 > URL: https://issues.jboss.org/browse/JBIDE-23179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > A vagrant machine in state not_created is not recognized at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22685) Eclipse marketplace entry for Freemarker IDE plugin

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22685?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22685. --------------------------------- Search on market place, automatic component suggestion after .ftl file opening, installing, everything is working. Closing. > Eclipse marketplace entry for Freemarker IDE plugin > --------------------------------------------------- > > Key: JBIDE-22685 > URL: https://issues.jboss.org/browse/JBIDE-22685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker, marketplace > Reporter: Paul Verest > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.1.Final > > > As initially proposed at https://github.com/jbosstools/jbosstools-freemarker issues, > just created https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools , it should appear within days. > Note, that this is now the only way for Eclipse to automatically discover and install Editor for .ftl files (and later for .ftlh and .fltx https://github.com/jbosstools/jbosstools-freemarker/pull/62) > Also it makes freemarker plugin searchable on marketplace, so solves new users questions http://stackoverflow.com/questions/9385561/freemarker-eclipse-plug-in -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-914) Integration Stack features have incorrect versions

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-914?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-914: -------------------------------- Assignee: Paul Leacu > Integration Stack features have incorrect versions > -------------------------------------------------- > > Key: JBTIS-914 > URL: https://issues.jboss.org/browse/JBTIS-914 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > > |com.jboss.devstudio.integration-stack.bpr.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.ds.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.fuse.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.soa.feature|9.0.2.CR1| > The version should be something like *9.0.1.GA-v20160808-1454-B27* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23170) Red Hat Central page auto-resizing gets broken after editing options

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23170?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-23170: ------------------------------- Attachment: jbosstools-central-webpage-2.0.0-SNAPSHOT.zip [~dgolovin] could you please try it with attached central webpage zip (using `-Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip`). I had very similar issue on Linux (Chrome and Firefox browsers) which is fixed in this central-webpage.zip (changes I made are here: https://github.com/rhopp/jbosstools-central-webpage/commit/ce2ed78bb2ebf1...) I hope these changes fixes the issue on your system also. I'll create a PR once you confirm it solves your issue. Thanks > Red Hat Central page auto-resizing gets broken after editing options > -------------------------------------------------------------------- > > Key: JBIDE-23170 > URL: https://issues.jboss.org/browse/JBIDE-23170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > Reporter: Denis Golovin > Priority: Minor > Attachments: 2016 09 14 2223 34.mp4, jbosstools-central-webpage-2.0.0-SNAPSHOT.zip > > > I noticed sometimes Red Hat Central stops resizing to editor part size and shows horizontal scrollbar. It happens when options button is clicked when editor part with central is maximized (see attached video). > !2016 09 14 2223 34.mp4! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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