[JBoss JIRA] (JBIDE-16019) Reorganize JST component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16019?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16019:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/214, https://github.com/jbosstools/jbosstools-jst/pull/231, https://github.com/jbosstools/jbosstools-javaee/pull/172, https://github.com/jbosstools/jbosstools-vpe/pull/192, https://github.com/jbosstools/jbosstools-central/pull/189 (was: https://github.com/jbosstools/jbosstools-base/pull/214, https://github.com/jbosstools/jbosstools-jst/pull/231, https://github.com/jbosstools/jbosstools-javaee/pull/172, https://github.com/jbosstools/jbosstools-vpe/pull/190, https://github.com/jbosstools/jbosstools-central/pull/189)
> Reorganize JST component
> ------------------------
>
> Key: JBIDE-16019
> URL: https://issues.jboss.org/browse/JBIDE-16019
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
> Attachments: dependencies.gliffy, dependencies.png
>
>
> !dependencies.png!
> My suggestions:
> *1. Clean up (remove obsolete plugins):*
> * jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
> * jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
> * jst.web.tiles/tiles.ui.
> *2. Fix dependency problem between jsp/html editor and other jsp/html editor related UI features (such as html5 property view) by merging all UI plugins into jst.web.ui plug-in:*
> * jst.jsp (JSP/HTML editor, content assist, outline)
> * jst.web.ui (palette, wizards, ...)
> * jst.text.ext (Open Ons)
> * jst.css (css editor)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16019) Reorganize JST component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16019?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16019:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/214, https://github.com/jbosstools/jbosstools-jst/pull/231, https://github.com/jbosstools/jbosstools-javaee/pull/172, https://github.com/jbosstools/jbosstools-vpe/pull/190, https://github.com/jbosstools/jbosstools-central/pull/189 (was: https://github.com/jbosstools/jbosstools-base/pull/214, https://github.com/jbosstools/jbosstools-jst/pull/229, https://github.com/jbosstools/jbosstools-javaee/pull/172, https://github.com/jbosstools/jbosstools-vpe/pull/190, https://github.com/jbosstools/jbosstools-central/pull/189)
> Reorganize JST component
> ------------------------
>
> Key: JBIDE-16019
> URL: https://issues.jboss.org/browse/JBIDE-16019
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
> Attachments: dependencies.gliffy, dependencies.png
>
>
> !dependencies.png!
> My suggestions:
> *1. Clean up (remove obsolete plugins):*
> * jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
> * jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
> * jst.web.tiles/tiles.ui.
> *2. Fix dependency problem between jsp/html editor and other jsp/html editor related UI features (such as html5 property view) by merging all UI plugins into jst.web.ui plug-in:*
> * jst.jsp (JSP/HTML editor, content assist, outline)
> * jst.web.ui (palette, wizards, ...)
> * jst.text.ext (Open Ons)
> * jst.css (css editor)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-15622:
----------------------------------
Description:
*Where to:*
1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog – report problem which may be not related with any exceptions
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
was:
*Where to:*
1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog – report problem which may be not related with any exceptions
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
>
> *Where to:*
> 1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog – report problem which may be not related with any exceptions
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16053) Aerogear: backbutton listener doesn't work on the android device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16053?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16053.
-------------------------------
Verified with JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> Aerogear: backbutton listener doesn't work on the android device
> ----------------------------------------------------------------
>
> Key: JBIDE-16053
> URL: https://issues.jboss.org/browse/JBIDE-16053
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.1.1.Final
>
>
> http://docs.phonegap.com/en/3.1.0/cordova_events_events.md.html#backbutton - backbutton event doc
> Steps for verifying:
> 1. Create new Hybrid Mobile Application Project
> 2. Update index.html with the sample from the documentation:
> {code:title=index.html|borderStyle=solid}
> <!DOCTYPE html>
> <html>
> <head>
> <title>Back Button Example</title>
> <script type="text/javascript" charset="utf-8" src="cordova.js"></script>
> <script type="text/javascript" charset="utf-8">
> // Wait for device API libraries to load
> //
> function onLoad() {
> document.addEventListener("deviceready", onDeviceReady, false);
> }
> // device APIs are available
> //
> function onDeviceReady() {
> // Register the event listener
> document.addEventListener("backbutton", onBackKeyDown, false);
> }
> // Handle the back button
> //
> function onBackKeyDown() {
> alert(1);
> }
> </script>
> </head>
> <body onload="onLoad()">
> </body>
> </html>
> {code}
> 3. Run the app on the android device
> 4. Press the back button when the app will be ready
> 5. ERROR: App will be closed - no alert will be shown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2833) CLONE - Installer fails due to spaces in JDK path on Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2833?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2833:
-------------------------------------
Should we fix it then? Fix for referenced JIRA was pushed in master branch as well.
> CLONE - Installer fails due to spaces in JDK path on Windows 8
> --------------------------------------------------------------
>
> Key: JBDS-2833
> URL: https://issues.jboss.org/browse/JBDS-2833
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.Alpha1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2833) CLONE - Installer fails due to spaces in JDK path on Windows 8
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2833?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-2833:
----------------------------------
I just cloned this from JBDS-2663 to verify it properly when QE receives first jbds 8.0.0.Alpha1 build.
> CLONE - Installer fails due to spaces in JDK path on Windows 8
> --------------------------------------------------------------
>
> Key: JBDS-2833
> URL: https://issues.jboss.org/browse/JBDS-2833
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.Alpha1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2663) Installer fails due to spaces in JDK path on Windows 8
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2663?page=com.atlassian.jira.plugin.... ]
Pavol Srna updated JBDS-2663:
-----------------------------
Fix Version/s: (was: 8.0.0.Alpha1)
> Installer fails due to spaces in JDK path on Windows 8
> ------------------------------------------------------
>
> Key: JBDS-2663
> URL: https://issues.jboss.org/browse/JBDS-2663
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Affects Versions: 7.0.0.Beta2
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months