March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24311: ------------------------------------- Steps to Reproduce: (was: # ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time) # EXEC: launch application wizard # EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page # EXEC: hit "< Back" Result: page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources. Expected result: the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again.) > Application wizard: is loading templates even if I go back > ---------------------------------------------------------- > > Key: JBIDE-24311 > URL: https://issues.jboss.org/browse/JBIDE-24311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Issue Type: Enhancement (was: Bug) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Issue Type: Task (was: Enhancement) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Description: I deployed the Camel Fuse Teampltes available in Fuse Tooling I restarted my Eclipse I reconnected to the same CDK - select application in OpenShift Instance view - go to Build Configs tab in properties view - select the element available Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) alternatively: * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... * create an app using the s2i-spring-boot-camel-xml template * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. steps: # I deployed the Camel Fuse Teampltes available in Fuse Tooling # I restarted my Eclipse # I reconnected to the same CDK # - select application in OpenShift Instance view # - go to Build Configs tab in properties view # - select the element available # Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) was: I deployed the Camel Fuse Teampltes available in Fuse Tooling I restarted my Eclipse I reconnected to the same CDK - select application in OpenShift Instance view - go to Build Configs tab in properties view - select the element available Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) alternatively: * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... * create an app using the s2i-spring-boot-camel-xml template * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. > steps: > # I deployed the Camel Fuse Teampltes available in Fuse Tooling > # I restarted my Eclipse > # I reconnected to the same CDK > # - select application in OpenShift Instance view > # - go to Build Configs tab in properties view > # - select the element available > # Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Issue Type: Feature Request (was: Bug) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Sprint: devex #147 April 2018 > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1 > > > In order to start Photon based builds, we need a working Photon based target platform -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25585) release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25585?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25585: ------------------------------- Sprint: devex #145 February 2018, devex #147 April 2018 (was: devex #145 February 2018) > release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25585 > URL: https://issues.jboss.org/browse/JBIDE-25585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM1, 4.6.0.Final > > > Need a semi-working placeholder (even if it's a CI build) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > Once we release 4.6.0.Final, we can then update the symlink to point here: > http://download.jboss.org/jbosstools/photon/stable/updates/ > Upstream issue: > https://bugs.eclipse.org/529801 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23771: ------------------------------------------ Afaik there's no solution to this. Shouldn't we resolve this as WONT_FIX? > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-19933. -------------------------------- Resolution: Out of Date Photon URLs should be already bootstrapped, and after that we probably won't need to do annual breaking releases so we'll just stay on photon / 12. > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.6.x) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 March 2018