August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3727: -------------------------------- Fix Version/s: 11.1.0.AM1 > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4408) DevSuite 1.4 Installer document how to clean up after a failed install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4408?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4408: -------------------------------- Fix Version/s: 11.0.0.GA > DevSuite 1.4 Installer document how to clean up after a failed install > ---------------------------------------------------------------------- > > Key: JBDS-4408 > URL: https://issues.jboss.org/browse/JBDS-4408 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: doc, ui > Fix For: 11.0.0.GA > > > There should be a document/faq that indicates how to clean-up / recover after a failed install. > On Windows there is the Uninstalli Dev Studio menu entry. But that doesn't clean up everything. > It prompts to delete everything in the installation directory C:\DeveloperSuite but doesn't actually delete everything. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4343) Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4343?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4343: -------------------------------- Fix Version/s: 11.x (was: 11.0.0.GA) > Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*' > ------------------------------------------------------------------------- > > Key: JBDS-4343 > URL: https://issues.jboss.org/browse/JBDS-4343 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.AM2 > Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: performance > Fix For: 11.x > > Attachments: install.png > > > The installer spends several minutes in this state: > !install.png|thumbnail! > Just for comparison > - AM1 installation takes total of about 2 minutes 15 seconds > - AM2 takes 5 minutes 40 seconds > There is no shortage of memory or disk I/O availability, the CPU is not topped off (even though AM2 eats up more CPU itself during this time). > DTRACE=true reveals nothing interesting really, this is what it says in the particular moment (notice how much time the operation takes): > {noformat} > Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64 > Preparing to commit the provisioning operation. > Committing the provisioning operation. > Operation completed in 289855 ms. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3730: -------------------------------- Fix Version/s: 11.x (was: 11.0.0.GA) > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.x > > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > 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! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4402) Devsuite 1.4 Windows re-runs installed component checks on expose events

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4402?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4402: -------------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.0.0.GA) > Devsuite 1.4 Windows re-runs installed component checks on expose events > ------------------------------------------------------------------------ > > Key: JBDS-4402 > URL: https://issues.jboss.org/browse/JBDS-4402 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: Windows 10 64-bit Pro, DevSuite 1.4 GA installer > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.1.0.AM1 > > > The DevSuite Windows installer re-runs the search for installed components every time there is a window event like restore/bring to front, minimize, etc. Considering how long it can take this can be quite annoying. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4405) DevSuite 1.4 installer links to CDK 2.4 docs for Hyper-V info

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4405?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4405: -------------------------------- Component/s: platform-installer (was: installer) > DevSuite 1.4 installer links to CDK 2.4 docs for Hyper-V info > ------------------------------------------------------------- > > Key: JBDS-4405 > URL: https://issues.jboss.org/browse/JBDS-4405 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Critical > Labels: ui > Fix For: 11.0.0.GA > > > The link for information about enabling Hyper-V in the installer brings up the CDK 2.4 documentation instead of the CDK 3.0 documentation. > Understand that this was probably necessary during development while the CDK 3.0 docs didn't exist. The problem is the link opens in a section describing CDK 2.4 software requirements which are inaccurate for CDK 3.0. > Is there any documentation for the DevSuite installer? > (Are there any other CDK 2.4 links that need to be updated in the installer?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3826) Some components fail with folder name containing non-standard characters

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3826: -------------------------------- Fix Version/s: 11.x (was: 11.0.0.GA) > Some components fail with folder name containing non-standard characters > ------------------------------------------------------------------------ > > Key: JBDS-3826 > URL: https://issues.jboss.org/browse/JBDS-3826 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.x > > > I have tried installing into this folder: > {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat} > And JBDS installation failed immediately, the install.log was not very helpful. > {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3826) Some components fail with folder name containing non-standard characters

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3826: -------------------------------- Labels: (was: havoc) > Some components fail with folder name containing non-standard characters > ------------------------------------------------------------------------ > > Key: JBDS-3826 > URL: https://issues.jboss.org/browse/JBDS-3826 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.x > > > I have tried installing into this folder: > {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat} > And JBDS installation failed immediately, the install.log was not very helpful. > {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3827) DevStudio installation fails when (windows) user has non-ascii chars in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3827: -------------------------------- Labels: (was: havoc) > DevStudio installation fails when (windows) user has non-ascii chars in the name > -------------------------------------------------------------------------------- > > Key: JBDS-3827 > URL: https://issues.jboss.org/browse/JBDS-3827 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1, 10.4.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.x > > > I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with: > {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml > - ERROR - > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.<init>(FileInputStream.java:138) > at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564) > at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86) > at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22443. -------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.x) Assignee: Nick Boldt Resolution: Out of Date > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: composite.install.test.log.txt > > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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