September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3954) Target Platform Requirements for JBDS 10.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3954?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3954: ---------------------------------- Duped by JBIDE-22889 and its linked issues. > Target Platform Requirements for JBDS 10.1.0.GA > ----------------------------------------------- > > Key: JBDS-3954 > URL: https://issues.jboss.org/browse/JBDS-3954 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification > Affects Versions: 10.1.0.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.1.0.GA > > > Track changes to third party inclusions in JBDS 10.1.0 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3954) Target Platform Requirements for JBDS 10.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3954?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3954: ----------------------------- Summary: Target Platform Requirements for JBDS 10.1.0.GA (was: Target Platform Requirements for JBDS 10.0.1.GA) > Target Platform Requirements for JBDS 10.1.0.GA > ----------------------------------------------- > > Key: JBDS-3954 > URL: https://issues.jboss.org/browse/JBDS-3954 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification > Affects Versions: 10.1.0.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.1.0.GA > > > Track changes to third party inclusions in JBDS 10.0.1 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3954) Target Platform Requirements for JBDS 10.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3954?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3954: ----------------------------- Description: Track changes to third party inclusions in JBDS 10.1.0 - target platforms, Central, Early Access, etc. (was: Track changes to third party inclusions in JBDS 10.0.1 - target platforms, Central, Early Access, etc.) > Target Platform Requirements for JBDS 10.1.0.GA > ----------------------------------------------- > > Key: JBDS-3954 > URL: https://issues.jboss.org/browse/JBDS-3954 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification > Affects Versions: 10.1.0.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.1.0.GA > > > Track changes to third party inclusions in JBDS 10.1.0 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8371) Query Parameters View: apply parameter value on focus lost

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8371?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8371: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Query Parameters View: apply parameter value on focus lost > ---------------------------------------------------------- > > Key: JBIDE-8371 > URL: https://issues.jboss.org/browse/JBIDE-8371 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.2.0.CR1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Fix For: 4.4.x > > > Test case: > 1. create query in HQL Editor: > from test.Message m where m.id = :id > 2. propulate the parameter in Parameters view > 3. change type to valid(integer) > 4. enter the value, but do not press Enter > 5. Run the query. > The value is not applied and considered as null. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4040) For JBDS 10.1.0.GA: Prepare for 4.4.1.Final / 10.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4040?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4040. ---------------------------- Assignee: Nick Boldt Resolution: Done > For JBDS 10.1.0.GA: Prepare for 4.4.1.Final / 10.1.0.GA > ------------------------------------------------------- > > Key: JBDS-4040 > URL: https://issues.jboss.org/browse/JBDS-4040 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.1.0.GA > > > For JBDS 10.1.0.GA: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA > [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch: > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.1.x > git push origin jbosstools-4.4.1.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too. > 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...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22626: ----------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22362: ----------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > 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.AM1 > > > 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, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22685?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22685. ------------------------------------ Resolution: Done Seems to be resolved. > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22803: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.x > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22773: ----------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.2.AM1 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- 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