December 2016 - jbosstools-issues

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4201: ------------------------------------- You're correct, we won't support this. I don't think it's necessary to say anything about this in the doc - by default, if something isn't documented, then it's not supported, right? So why document it only to say it's not supported? I'll be happy to hear what others think :) > 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)

7 years, 7 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: --------------------------------------- I think that I identified what this lugin should be configured to do: - with incremental build, it should build the "Source" that will be used by Eclipse OpenShift Tooling to hot deploy in OpenShift instance To determine: - what is the goal/phase to generate this full "Source" - how to configure Eclipse OpenShift Tooling to look at the right "Source" for projects using fabric8 > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4211) Change yum repository configuration

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4211?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4211. ------------------------------ Thank you. The install guide will be updated in RHDEVDOCS-309. > Change yum repository configuration > ----------------------------------- > > Key: JBDS-4211 > URL: https://issues.jboss.org/browse/JBDS-4211 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: rpm > Affects Versions: 10.3.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.2.0.GA > > > I spoke with [~vkadlcik] about yum repository configuration. Václav has proposed to remove these lines from config file: > * sslverify=0 > Vašek said: _If it mean that user have to install some certification then this fact should be mentioned in documentation._ > I removed this parameter and I was still able to install RPM. I didn't have to install any certification, so we can remove this parameter I guess. > * gpgcheck=0 > GPG check should be enabled (but we have to sign RPM package JBDS-4197) > * includepkgs=rh-eclipse* > we don't need that > * skip_if_unavailable=1 > This feature is disabled by default. We haven't reason to change this behaviour. It might seems that we are not able to keep our repository online. It depends on the user if he would like to skip unavailable repositories. > We need to update this guide https://devstudio.jboss.com/10.0/snapshots/rpms/10.3.0/x86_64/ > and we also need to update install guide (CC:[~supriya.bharadwaj]) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21857: --------------------------------------- Well I will reiterate myself again. This JIRA is precisely about the way how it is at the moment still bugged - HCR failed dialog on further HCR compatible changes after module restart is still shown, although this JIRA is supposed to fix it. Continuing when HCR Failed dialog is shown after HCR compatible changes are done does not work for code redeployment, although this JIRA is supposed to fix it. I would *definitely* do not close this one as resolved. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

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

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-4201: --------------------------------- >From the meeting minutes, I understand that we have voted to not support this feature. It's probably worth noting in the installation doc that this way is available but not supported to prevent potential issues. > 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)

7 years, 7 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 commented on JBDS-4197: ---------------------------------- First draft of the signing process used for devstudio 10.2 rpm: https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/8ed9449afda3d127... TODO: wrap a job around this and run it on Wonka (needs createrepo_c and permission to write to RHDS and JBDS servers). > 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)

7 years, 7 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 updated JBDS-4197: ----------------------------- Fix Version/s: 10.2.0.GA (was: 10.3.0.GA) > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4211) Change yum repository configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4211?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4211: ---------------------------------- https://github.com/jbdevstudio/jbdevstudio-product/commit/efd36e83a250def... This will roll out to the 10.3.0 snapshot site the next time a build fires. > Change yum repository configuration > ----------------------------------- > > Key: JBDS-4211 > URL: https://issues.jboss.org/browse/JBDS-4211 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: rpm > Affects Versions: 10.3.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.2.0.GA > > > I spoke with [~vkadlcik] about yum repository configuration. Václav has proposed to remove these lines from config file: > * sslverify=0 > Vašek said: _If it mean that user have to install some certification then this fact should be mentioned in documentation._ > I removed this parameter and I was still able to install RPM. I didn't have to install any certification, so we can remove this parameter I guess. > * gpgcheck=0 > GPG check should be enabled (but we have to sign RPM package JBDS-4197) > * includepkgs=rh-eclipse* > we don't need that > * skip_if_unavailable=1 > This feature is disabled by default. We haven't reason to change this behaviour. It might seems that we are not able to keep our repository online. It depends on the user if he would like to skip unavailable repositories. > We need to update this guide https://devstudio.jboss.com/10.0/snapshots/rpms/10.3.0/x86_64/ > and we also need to update install guide (CC:[~supriya.bharadwaj]) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4211) Change yum repository configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4211?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4211: ---------------------------------- Since I had to update the README for the staging sites anyway to add instructions for adding the gpg key, figured I could do this too. https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.2.0.GA-buil... http://www.qa.jboss.com/binaries/devstudio/10.0/staging/builds/devstudio-... So... fixed in 4.4.2.x and master branches. > Change yum repository configuration > ----------------------------------- > > Key: JBDS-4211 > URL: https://issues.jboss.org/browse/JBDS-4211 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: rpm > Affects Versions: 10.3.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.2.0.GA > > > I spoke with [~vkadlcik] about yum repository configuration. Václav has proposed to remove these lines from config file: > * sslverify=0 > Vašek said: _If it mean that user have to install some certification then this fact should be mentioned in documentation._ > I removed this parameter and I was still able to install RPM. I didn't have to install any certification, so we can remove this parameter I guess. > * gpgcheck=0 > GPG check should be enabled (but we have to sign RPM package JBDS-4197) > * includepkgs=rh-eclipse* > we don't need that > * skip_if_unavailable=1 > This feature is disabled by default. We haven't reason to change this behaviour. It might seems that we are not able to keep our repository online. It depends on the user if he would like to skip unavailable repositories. > We need to update this guide https://devstudio.jboss.com/10.0/snapshots/rpms/10.3.0/x86_64/ > and we also need to update install guide (CC:[~supriya.bharadwaj]) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4211) Change yum repository configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4211?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4211. ------------------------------ Resolution: Done > Change yum repository configuration > ----------------------------------- > > Key: JBDS-4211 > URL: https://issues.jboss.org/browse/JBDS-4211 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: rpm > Affects Versions: 10.3.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.2.0.GA > > > I spoke with [~vkadlcik] about yum repository configuration. Václav has proposed to remove these lines from config file: > * sslverify=0 > Vašek said: _If it mean that user have to install some certification then this fact should be mentioned in documentation._ > I removed this parameter and I was still able to install RPM. I didn't have to install any certification, so we can remove this parameter I guess. > * gpgcheck=0 > GPG check should be enabled (but we have to sign RPM package JBDS-4197) > * includepkgs=rh-eclipse* > we don't need that > * skip_if_unavailable=1 > This feature is disabled by default. We haven't reason to change this behaviour. It might seems that we are not able to keep our repository online. It depends on the user if he would like to skip unavailable repositories. > We need to update this guide https://devstudio.jboss.com/10.0/snapshots/rpms/10.3.0/x86_64/ > and we also need to update install guide (CC:[~supriya.bharadwaj]) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016