December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-18743) [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18743: ------------------------------------ I've updated https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... to do better checking and support a -fn flag to report all the 404s instead of stopping on the first one. It can now be run against a set of URLs, too. So rather than using p2browser and parsing the log, we can run this against a set of URLs to validate, and use the console log parser to report any problems. Here's a job-in-progress we can enhance to parse the ide-config.properrties file, so that all the composite sites are validated. Then I forked that file to make its output cleaner and support recursion: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... I've already found one broken URL: {code} $➔ ./validateCompositeSites.sh http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... [INFO] Checking for valid children in: http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... {1/1} [1/1] http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... : NO [INFO] URLs found: 0 [ERROR] URLs missing: 1 {code} > [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18743 at 12/13/17 4:03 PM: -------------------------------------------------------------- I've updated https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... to do better checking and support a -fn flag to report all the 404s instead of stopping on the first one. It can now be run against a set of URLs, too. So rather than using p2browser and parsing the log, we can run this against a set of URLs to validate, and use the console log parser to report any problems. Then I forked that file to make its output cleaner and support recursion: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... Here's a job-in-progress we can enhance to parse the ide-config.properrties file, so that all the composite sites are validated. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... I've already found one broken URL: {code} $➔ ./validateCompositeSites.sh http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... [INFO] Checking for valid children in: http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... {1/1} [1/1] http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... : NO [INFO] URLs found: 0 [ERROR] URLs missing: 1 {code} was (Author: nickboldt): I've updated https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... to do better checking and support a -fn flag to report all the 404s instead of stopping on the first one. It can now be run against a set of URLs, too. So rather than using p2browser and parsing the log, we can run this against a set of URLs to validate, and use the console log parser to report any problems. Here's a job-in-progress we can enhance to parse the ide-config.properrties file, so that all the composite sites are validated. Then I forked that file to make its output cleaner and support recursion: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/valida... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... I've already found one broken URL: {code} $➔ ./validateCompositeSites.sh http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... [INFO] Checking for valid children in: http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... {1/1} [1/1] http://download.jboss.org/jbosstools/oxygen/development/updates/integrati... : NO [INFO] URLs found: 0 [ERROR] URLs missing: 1 {code} > [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25303: ------------------------------------------ [~rob.stryker] can you please chime in with what's missing? > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM3 > > Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-554) Update rh-eclipse47 collection to Oxygen.2 bits

by Martha Benitez (JIRA)

[ https://issues.jboss.org/browse/ERT-554?page=com.atlassian.jira.plugin.sy... ] Martha Benitez updated ERT-554: ------------------------------- Summary: Update rh-eclipse47 collection to Oxygen.2 bits (was: Build Oxygen.2 for SCL) > Update rh-eclipse47 collection to Oxygen.2 bits > ----------------------------------------------- > > Key: ERT-554 > URL: https://issues.jboss.org/browse/ERT-554 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Mat Booth > Assignee: Mat Booth > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25505) New application wizard: Configure > Deploy to OpenShift wont create a server adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25505?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25505: ------------------------------------------ [~dbocharov] CC (just for your FYI since you work on JBIDE-24961) > New application wizard: Configure > Deploy to OpenShift wont create a server adapter > ------------------------------------------------------------------------------------ > > Key: JBIDE-25505 > URL: https://issues.jboss.org/browse/JBIDE-25505 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Labels: application_wizard, configure_openshift, openshift_v3 > Fix For: 4.5.x > > > steps: > # ASSERT: have a project in your workspace. The project has to be git shared with an origin pointing to the internet. (to create it ex. create an app in OpenShift via template, import it to the workspace and then kill the OpenShift app) > # EXEC: in the context menu to your workspace project pick Configure > Deploy to OpenShift and step through the wizard until the end > Result: > You're never asked if you want to create a server adapter. And there is no server adapter being created. While if you go File > New > Other > OpenShift Application and create an app, you get asked if you want to create a server adapter. And it gets created if you agree to. > Expected result: > A server adapter is created -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25505) New application wizard: Configure > Deploy to OpenShift wont create a server adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25505?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25505: ------------------------------------- Labels: application_wizard configure_openshift openshift_v3 (was: ) > New application wizard: Configure > Deploy to OpenShift wont create a server adapter > ------------------------------------------------------------------------------------ > > Key: JBIDE-25505 > URL: https://issues.jboss.org/browse/JBIDE-25505 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Labels: application_wizard, configure_openshift, openshift_v3 > Fix For: 4.5.x > > > steps: > # ASSERT: have a project in your workspace. The project has to be git shared with an origin pointing to the internet. (to create it ex. create an app in OpenShift via template, import it to the workspace and then kill the OpenShift app) > # EXEC: in the context menu to your workspace project pick Configure > Deploy to OpenShift and step through the wizard until the end > Result: > You're never asked if you want to create a server adapter. And there is no server adapter being created. While if you go File > New > Other > OpenShift Application and create an app, you get asked if you want to create a server adapter. And it gets created if you agree to. > Expected result: > A server adapter is created -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25505) New application wizard: Configure > Deploy to OpenShift wont create a server adapter

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25505: ---------------------------------------- Summary: New application wizard: Configure > Deploy to OpenShift wont create a server adapter Key: JBIDE-25505 URL: https://issues.jboss.org/browse/JBIDE-25505 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.2.AM2 Reporter: Andre Dietisheim Fix For: 4.5.x steps: # ASSERT: have a project in your workspace. The project has to be git shared with an origin pointing to the internet. (to create it ex. create an app in OpenShift via template, import it to the workspace and then kill the OpenShift app) # EXEC: in the context menu to your workspace project pick Configure > Deploy to OpenShift and step through the wizard until the end Result: You're never asked if you want to create a server adapter. And there is no server adapter being created. While if you go File > New > Other > OpenShift Application and create an app, you get asked if you want to create a server adapter. And it gets created if you agree to. Expected result: A server adapter is created -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25295) Cannot use minishift binary instead of CDK in CDK server adapter in IDE

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25295?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25295: ------------------------------- Fix Version/s: 4.5.2.AM3 (was: 4.5.x) > Cannot use minishift binary instead of CDK in CDK server adapter in IDE > ----------------------------------------------------------------------- > > Key: JBIDE-25295 > URL: https://issues.jboss.org/browse/JBIDE-25295 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.2.AM3 > > Attachments: Screenshot_20171025_134414.png > > > I am curious what if user will want to use upstream minishift binary for CDK 3.x (3.2+) server adapter. It is not possible now. > Is there a reason for not allowing user to use upstream minishift binary? Before we did not distinguish between CDK 3.1 and 3.2, it was possible in my opinion. We lost this option when new adapter was added and we started to check CDK v.3.x.x version string for two CDK 3.1 and CDK 3.2 binaries. > [~rob.stryker] [~jeffmaury] [~mmalina] WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25349) Renaming of existing CDK server adapter is not applied everywhere

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25349?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25349: ------------------------------- Fix Version/s: 4.5.2.AM3 (was: 4.5.x) > Renaming of existing CDK server adapter is not applied everywhere > ----------------------------------------------------------------- > > Key: JBIDE-25349 > URL: https://issues.jboss.org/browse/JBIDE-25349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.2.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25288) JMX Connection on OpenShift server adapter are not updated on pod updates

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25288?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25288: ------------------------------- Fix Version/s: 4.5.2.AM3 (was: 4.5.x) > JMX Connection on OpenShift server adapter are not updated on pod updates > ------------------------------------------------------------------------- > > Key: JBIDE-25288 > URL: https://issues.jboss.org/browse/JBIDE-25288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Affects Versions: 4.5.0.Final, 4.5.1.AM3 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.2.AM3 > > > OpenShift Server Adapters are handling pod updates except for JMX Connection. > The connection url contains the pod name but it is never updated when the pod name is updated on the OpenShift instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017