October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-4131: ------------------------------------- [~nickboldt], Could you, please, try the following: - open the second page of the New Project Example wizard - disable the "Use default Workspace location" checkbox - select a non-default location - finish the wizard Also, try to create a project using the New Maven Project wizard. The JBoss New Project Example wizard uses the m2e wizard page when importing a maven archetype. > Can't import example project after RPM installation on RHEL 7 > ------------------------------------------------------------- > > Key: JBDS-4131 > URL: https://issues.jboss.org/browse/JBDS-4131 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL Server 7.2. > Reporter: Lukáš Valach > Assignee: Snjezana Peco > Fix For: 10.2.0.AM3 > > Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, import_wizard.png, rh-eclipse46-devstudio.repo > > > During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens. > There is one warning and many errors in Error Log View. > Error log export: [^DevstudiErrorLog.txt] > I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-23412: ---------------------------------- Assignee: (was: Pavol Srna) > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_latest, scaling_pods_wizard > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) unresolved shared libraries when installing rh-eclipse46-devstudio rpm

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4059: --------------------------------- Component/s: rpm > unresolved shared libraries when installing rh-eclipse46-devstudio rpm > ---------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-23412: ---------------------------------- Assignee: Pavol Srna > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Pavol Srna > Labels: deploy_latest, scaling_pods_wizard > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22362: ------------------------------------- [~adietish] great that you figure out the cause! So, as I understand for now this issue is blocked by JBIDE-23412 > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-947: ---------------------------------- [~apodhrad] [~lhein] - Hey - I believe this is exactly how this is expected to work. Remember that there copuld be loadable runtimes from DataVirt or BRMS so it's supposed to be a discovery. There could also (unlikely) be multiiple runtimes. > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-948 at 10/24/16 3:09 PM: ------------------------------------------------------------ Hey [~apodhrad] a little confused by this one. 1. Install devstudio 10.1.0.GA I presume? {code} java -jar devstudio-10.1.0.GA-v20160902-1725-B43-installer-standalone.jar {code} 2. I can find InstallConfigRecord.xml in the devstudio I just created. 3. Delete the devstudio folder that contains InstallConfigRecord.xml? Can I just run your command and point to a different devstudio installation location? When I do I get: {code} [pleacu@pleacu-2-laptop crap]$ java -jar ~/install/devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar InstallConfigRecord.xml [ Starting automated installation ] [INFO] Selected JVM Information [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-1.b14.fc24.x86_64 [INFO] Vendor : Oracle Corporation [INFO] Version : 1.8.0_102 [INFO] Arch : 64-bit java.lang.NullPointerException java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:459) at java.util.Properties.setProperty(Properties.java:166) at com.izforge.izpack.installer.AutomatedInstallData.setVariable(Unknown Source) at com.jboss.devstudio.core.installer.InstallAdditionalRuntimesPanelAutomationHelper.runAutomated(InstallAdditionalRuntimesPanelAutomationHelper.java:38) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) at com.izforge.izpack.installer.Installer.main(Unknown Source) [ Automated installation FAILED! ] {code} This might be my version of Java - it seems a little flaky. was (Author: pleacu): Hey [~apodhrad] a little confused by this one. 1. Install devstudio 10.1.0.GA I presume? {code} java -jar devstudio-10.1.0.GA-v20160902-1725-B43-installer-standalone.jar {code} 2. I can find InstallConfigRecord.xml in the devstudio I just created. 3. Delete the devstudio folder that contains InstallConfigRecord.xml? Can I just run your command and point to a different devstudio installation location? When I do I get: {code} [pleacu@pleacu-2-laptop crap]$ java -jar ~/install/devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar InstallConfigRecord.xml [ Starting automated installation ] [INFO] Selected JVM Information [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-1.b14.fc24.x86_64 [INFO] Vendor : Oracle Corporation [INFO] Version : 1.8.0_102 [INFO] Arch : 64-bit java.lang.NullPointerException java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:459) at java.util.Properties.setProperty(Properties.java:166) at com.izforge.izpack.installer.AutomatedInstallData.setVariable(Unknown Source) at com.jboss.devstudio.core.installer.InstallAdditionalRuntimesPanelAutomationHelper.runAutomated(InstallAdditionalRuntimesPanelAutomationHelper.java:38) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) at com.izforge.izpack.installer.Installer.main(Unknown Source) [ Automated installation FAILED! ] {code} > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-948: ---------------------------------- Hey [~apodhrad] a little confused by this one. 1. Install devstudio 10.1.0.GA I presume? {code} java -jar devstudio-10.1.0.GA-v20160902-1725-B43-installer-standalone.jar {code} 2. I can find InstallConfigRecord.xml in the devstudio I just created. 3. Delete the devstudio folder that contains InstallConfigRecord.xml? Can I just run your command and point to a different devstudio installation location? When I do I get: {code} [pleacu@pleacu-2-laptop crap]$ java -jar ~/install/devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar InstallConfigRecord.xml [ Starting automated installation ] [INFO] Selected JVM Information [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-1.b14.fc24.x86_64 [INFO] Vendor : Oracle Corporation [INFO] Version : 1.8.0_102 [INFO] Arch : 64-bit java.lang.NullPointerException java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:459) at java.util.Properties.setProperty(Properties.java:166) at com.izforge.izpack.installer.AutomatedInstallData.setVariable(Unknown Source) at com.jboss.devstudio.core.installer.InstallAdditionalRuntimesPanelAutomationHelper.runAutomated(InstallAdditionalRuntimesPanelAutomationHelper.java:38) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) at com.izforge.izpack.installer.Installer.main(Unknown Source) [ Automated installation FAILED! ] {code} > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23412: ------------------------------------------ [~jeffmaury] [~bdshadow] This bug is rather nasty (but either rather easy to fix via a bug in our queries - ResourceUtils/ServiceResourceMapper or rather hard and a cache issue). I believe that quite of few other actions on resources might be affected (did not verify though). > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_latest, scaling_pods_wizard > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Story Points: 8 Workaround Description: Restart Eclipse :( Workaround: Workaround Exists Priority: Major (was: Critical) > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_latest, scaling_pods_wizard > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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