December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4201: ------------------------------------- IzPack provides three way to run installation from installer jar: 1. GUI installation {code}java -jar installer.jar{code} 2. Automated headless (no GUI) installation, when all required input like target location, what to install and etc comes from xml file {code}java -jar installer.jar automation-data.xml{code} 3. Console headless installation, when all user interaction is done through console input/output in terminal {code}java -jar installer.jar -console{code} 4. (1) in some cases triggers (3) when executed from console probably due to upstream issue in older releases of OpenJDK on Fedora. I think it worth to mention installation types and say that (3) is not supported in case someone hit (4) scenario. Because they now removed old documentation site for IzPack 4 and created new one here https://izpack.atlassian.net/wiki/display/IZPACK/IzPack+4. Problem is it has no info about installation types at all. > CLI-only installation is available but does not provide necessary info > ---------------------------------------------------------------------- > > Key: JBDS-4201 > URL: https://issues.jboss.org/browse/JBDS-4201 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Fix For: 10.x > > Attachments: InstallConfigRecord.xml > > > I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected. > Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it. > My questions here are: > - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens. > - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion. > Any thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ fixed 'co' -> 'git checkout' in the two jobs that create the emails. fixed path to getProjectRootPomParents.sh as `pwd`/util/getProjectRootPomParents.sh Also added line joins in the text passed to --fulltext: https://github.com/jbosstools/jbosstools-build-ci/commit/65d7a63ac8b88134... We'll see if that works better when we move to the AM2 parent pom in a few weeks. > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23599) Integration tests global refactoring: org.jboss.tools.docker.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23599?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23599: ------------------------------------- Description: Maven command: {code} mvn clean verify -Dtest.module=org.jboss.tools.docker.ui.bot.test -Dusage_reporting_enabled=false -DdockerServerURI=tcp://localhost:2375 -DunixSocket=unix:///var/run/docker.sock -DsearchConnection=true -DdockerHubUsername=<dockerhub-username> -DdockerHubEmail=<dockerhub-email> -DdockerHubPassword=<dockerhub-pw> -DskipTests=false {code} was: Maven command: {code} mvn clean verify -Dtest.module=org.jboss.tools.docker.ui.bot.test -DskipTests=false {code} > Integration tests global refactoring: org.jboss.tools.docker.ui.bot.test > ------------------------------------------------------------------------ > > Key: JBIDE-23599 > URL: https://issues.jboss.org/browse/JBIDE-23599 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: docker, integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.docker.ui.bot.test -Dusage_reporting_enabled=false -DdockerServerURI=tcp://localhost:2375 -DunixSocket=unix:///var/run/docker.sock -DsearchConnection=true -DdockerHubUsername=<dockerhub-username> -DdockerHubEmail=<dockerhub-email> -DdockerHubPassword=<dockerhub-pw> -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4197) sign devstudio rpm & document the process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4197?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4197. ------------------------------ Resolution: Done Doc: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... Jobs: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/view/devstudio/job/jbossto... http://wonka.mw.lab.eng.bos.redhat.com/jenkins/view/devstudio/job/jbossto... > sign devstudio rpm & document the process > ----------------------------------------- > > Key: JBDS-4197 > URL: https://issues.jboss.org/browse/JBDS-4197 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.2.0.GA > > Attachments: devstudiol.rpm.3rdparty.deps.txt > > > For the GA build of the devstudio rpm, I need to: > * sign the rpm [1] > * document the steps in the release guide [2] > [1] https://engineering.redhat.com/docs/en-US/Policy/30.se/html/Security_Engi... > [2] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23597) Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23597: ------------------------------------------ [~rawagner] please review https://github.com/jbosstools/jbosstools-integration-tests/pull/1688 > Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23597 > URL: https://issues.jboss.org/browse/JBIDE-23597 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, ticketmonster > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.usercase.ticketmonster.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23597) Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23597: ------------------------------------------ Ticketmonster isnt maintainted any more. So there's no value for this test any more. > Integration tests global refactoring: org.jboss.tools.usercase.ticketmonster.ui.bot.test > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23597 > URL: https://issues.jboss.org/browse/JBIDE-23597 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, ticketmonster > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.usercase.ticketmonster.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-999) Add Consume SOAP Digest test + update Consume REST/SOAP tests

by stanislav kaleta (JIRA)

stanislav kaleta created JBTIS-999: -------------------------------------- Summary: Add Consume SOAP Digest test + update Consume REST/SOAP tests Key: JBTIS-999 URL: https://issues.jboss.org/browse/JBTIS-999 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.4.0.Final, 4.3.3.Final Reporter: stanislav kaleta Assignee: Andrej Podhradsky Fix For: 4.4.0.Final, 4.3.3.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- [~chirino][~jeffmaury] the BuildConfig == the "Source" of the image to be deployed? Or it describes the "Source"? Or I'm completely aside... > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23625: ---------------------------------------- Summary: JMX: jmx tree is not very usable Key: JBIDE-23625 URL: https://issues.jboss.org/browse/JBIDE-23625 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.2.Final Reporter: Andre Dietisheim Fix For: 4.4.3.AM1 Attachments: image-2016-12-02-16-47-59-519.png steps to reproduce: # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project # EXEC: create a server adapter for it # ASSERT: your server adapter now has a JMX child node # EXEC: double click it and wait until all MBeans are loaded # EXEC: now try to see if you can find your deployment Result: You get a listing of tons of beans. !mbeans.png! Your deployment is a child bean of jboss.as, named by the war that was created: !mbean-deployment.png! Rather painfull to find a listing of your deployments in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23622) Build Log: impossible to get logs once the build pod is completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23622: --------------------------------------- I am ok with changing it, but I don't agree that you cant get logs of completed pod (original title "Cannot get log of completed build pod"). And getting log of a specific build via oc binary is possible with "oc logs eap-app-1-build". The command you pasted in description get you latest build. Even via oc binary you can get previous logs of failing pods, which are not in running state by providing flag --previous=true. But I am ok with description as it is now. > Build Log: impossible to get logs once the build pod is completed > ----------------------------------------------------------------- > > Key: JBIDE-23622 > URL: https://issues.jboss.org/browse/JBIDE-23622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: build_log, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: cannot-build-log.png, log_build.png > > > When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog > !log_build.png! > There is no error in log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 2016