August 2016 - jbosstools-issues - Jboss List Archives

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: Openshift Web Console.png > 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.1.Final > > 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-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22803: ------------------------------------ [~dbocharov] I was able to reproduce. Just after application creation (the second time) !after application creation.png! After the build has finished: !after build finished.png! Openshift Web Console: !Openshift Web Console.png! > 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.1.Final > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, Openshit 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-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: (was: Openshit Web Console.png) > 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.1.Final > > 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-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: Openshit Web Console.png > 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.1.Final > > Attachments: after application creation.png, after build finished.png, Openshit 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-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: after build finished.png > 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.1.Final > > Attachments: after application creation.png, after build finished.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-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: after application creation.png > 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.1.Final > > Attachments: after application creation.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-22446) Release process should disallow inclusion of snapshots artifacts

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22446: --------------------------------------- Nope, [~nickboldt], it was not RC1, the dependency was SNAPSHOT - I tried this on August 9 and it was still SNAPSHOT (I checked that). If you look at the repo history you will see that it was changed from SNAPSHOT to RC1 2 days after I tried it: https://github.com/jbosstools/jbosstools-openshift/commit/9213c7febc4afe3... But if you're saying that setting -DBUILD_ALIAS from command line won't change a thing, then that's another thing - that would then explain it. I don't see a reason why the command line argument shouldn't be honored just like it is for the rest of maven, but it depends on how hard it is to achieve that. BTW, I did do the steps you suggested and it worked. And when I reverted the revert (i.e. moved back to RC1 rest client), the build passed as expected. Good to see it works. > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22726?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22726. ------------------------------- Looks good to me, closing. > Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22726 > URL: https://issues.jboss.org/browse/JBIDE-22726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM3 > > > I need a list of file extensions we want associated with JBT/devstudio. > Then I can add those to the list of tags on the marketplace entries: > https://marketplace.eclipse.org/content/jboss-tools > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio > eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] > ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... > ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) > [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4006) Unable to add nested <when> in Camel - Blueprint

by Abel BOUCHAMA (JIRA)

[ https://issues.jboss.org/browse/JBDS-4006?page=com.atlassian.jira.plugin.... ] Abel BOUCHAMA commented on JBDS-4006: ------------------------------------- [~mickael_istria]: Done, you can close the ticket now. thx > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBDS-4006 > URL: https://issues.jboss.org/browse/JBDS-4006 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Reporter: Abel BOUCHAMA > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4006) Unable to add nested <when> in Camel - Blueprint

by Abel BOUCHAMA (JIRA)

[ https://issues.jboss.org/browse/JBDS-4006?page=com.atlassian.jira.plugin.... ] Abel BOUCHAMA edited comment on JBDS-4006 at 8/18/16 3:45 AM: -------------------------------------------------------------- I have tried in JBDS version 9.0, but i got always the same behaviour. > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBDS-4006 > URL: https://issues.jboss.org/browse/JBDS-4006 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Reporter: Abel BOUCHAMA > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- 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 August 2016