[JBoss JIRA] (JBDS-3405) Installer step 4 empty and NPE thrown
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3405?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3405:
--------------------------------
Fix Version/s: 9.0.0.Alpha2
> Installer step 4 empty and NPE thrown
> -------------------------------------
>
> Key: JBDS-3405
> URL: https://issues.jboss.org/browse/JBDS-3405
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Alpha2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
> Attachments: step4-empty.png
>
>
> When you try to install JBDS using the standalone installer, in Step 4: Select Java VM, the page is empty and there is a NPE thrown in the terminal:
> {code}
> nattura:9.0.0 rasp$ java -jar jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar
> java.lang.NullPointerException
> at com.jboss.devstudio.core.installer.JREPathPanel.change(JREPathPanel.java:483)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.fireChange(PathSelectionPanel.java:237)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.access$000(PathSelectionPanel.java:34)
> at com.jboss.devstudio.core.installer.PathSelectionPanel$1.insertUpdate(PathSelectionPanel.java:101)
> at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:202)
> at javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:749)
> at javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:708)
> at javax.swing.text.PlainDocument.insertString(PlainDocument.java:130)
> at javax.swing.text.AbstractDocument.replace(AbstractDocument.java:670)
> at javax.swing.text.JTextComponent.setText(JTextComponent.java:1718)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.setPath(PathSelectionPanel.java:202)
> at com.jboss.devstudio.core.installer.JREPathPanel.updateJava(JREPathPanel.java:287)
> at com.jboss.devstudio.core.installer.JREPathPanel.panelActivate(JREPathPanel.java:273)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585)
> at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
> at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
> at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
> at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
> at java.awt.Component.processMouseEvent(Component.java:6516)
> at javax.swing.JComponent.processMouseEvent(JComponent.java:3320)
> at java.awt.Component.processEvent(Component.java:6281)
> at java.awt.Container.processEvent(Container.java:2229)
> at java.awt.Component.dispatchEventImpl(Component.java:4872)
> at java.awt.Container.dispatchEventImpl(Container.java:2287)
> at java.awt.Component.dispatchEvent(Component.java:4698)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
> at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
> at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
> at java.awt.Container.dispatchEventImpl(Container.java:2273)
> at java.awt.Window.dispatchEventImpl(Window.java:2719)
> at java.awt.Component.dispatchEvent(Component.java:4698)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735)
> at java.awt.EventQueue.access$200(EventQueue.java:103)
> at java.awt.EventQueue$3.run(EventQueue.java:694)
> at java.awt.EventQueue$3.run(EventQueue.java:692)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
> at java.awt.EventQueue$4.run(EventQueue.java:708)
> at java.awt.EventQueue$4.run(EventQueue.java:706)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:705)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
> {code}
> !step4-empty.png!
> When you go back one page and forth again, it will work then.
> BTW, this happens on JBDS 9.0.0.Alpha2 nightly build from master - jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar . And it happens to me on OS X 10.10 Yosemite with java 7 and the same thing happened to [~psrna] also on OS X today.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3405) Installer step 4 empty and NPE thrown
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3405?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3405:
-----------------------------------
Assignee: Denis Golovin
> Installer step 4 empty and NPE thrown
> -------------------------------------
>
> Key: JBDS-3405
> URL: https://issues.jboss.org/browse/JBDS-3405
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Alpha2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Attachments: step4-empty.png
>
>
> When you try to install JBDS using the standalone installer, in Step 4: Select Java VM, the page is empty and there is a NPE thrown in the terminal:
> {code}
> nattura:9.0.0 rasp$ java -jar jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar
> java.lang.NullPointerException
> at com.jboss.devstudio.core.installer.JREPathPanel.change(JREPathPanel.java:483)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.fireChange(PathSelectionPanel.java:237)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.access$000(PathSelectionPanel.java:34)
> at com.jboss.devstudio.core.installer.PathSelectionPanel$1.insertUpdate(PathSelectionPanel.java:101)
> at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:202)
> at javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:749)
> at javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:708)
> at javax.swing.text.PlainDocument.insertString(PlainDocument.java:130)
> at javax.swing.text.AbstractDocument.replace(AbstractDocument.java:670)
> at javax.swing.text.JTextComponent.setText(JTextComponent.java:1718)
> at com.jboss.devstudio.core.installer.PathSelectionPanel.setPath(PathSelectionPanel.java:202)
> at com.jboss.devstudio.core.installer.JREPathPanel.updateJava(JREPathPanel.java:287)
> at com.jboss.devstudio.core.installer.JREPathPanel.panelActivate(JREPathPanel.java:273)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585)
> at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
> at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
> at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
> at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
> at java.awt.Component.processMouseEvent(Component.java:6516)
> at javax.swing.JComponent.processMouseEvent(JComponent.java:3320)
> at java.awt.Component.processEvent(Component.java:6281)
> at java.awt.Container.processEvent(Container.java:2229)
> at java.awt.Component.dispatchEventImpl(Component.java:4872)
> at java.awt.Container.dispatchEventImpl(Container.java:2287)
> at java.awt.Component.dispatchEvent(Component.java:4698)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
> at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
> at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
> at java.awt.Container.dispatchEventImpl(Container.java:2273)
> at java.awt.Window.dispatchEventImpl(Window.java:2719)
> at java.awt.Component.dispatchEvent(Component.java:4698)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735)
> at java.awt.EventQueue.access$200(EventQueue.java:103)
> at java.awt.EventQueue$3.run(EventQueue.java:694)
> at java.awt.EventQueue$3.run(EventQueue.java:692)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
> at java.awt.EventQueue$4.run(EventQueue.java:708)
> at java.awt.EventQueue$4.run(EventQueue.java:706)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:705)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
> {code}
> !step4-empty.png!
> When you go back one page and forth again, it will work then.
> BTW, this happens on JBDS 9.0.0.Alpha2 nightly build from master - jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar . And it happens to me on OS X 10.10 Yosemite with java 7 and the same thing happened to [~psrna] also on OS X today.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ]
Konstantin Marmalyukov commented on JBDS-3263:
----------------------------------------------
{quote}so 53 mb's is a signficant part - is the 25 mb windows, 25 mb linux binaries ?{quote}
it's likely ~17mb for win32 and 34mb for linux32 and linux64 :)
{quote}1.c - I don't understand this change, why would stop asking the user ? the user is the one deciding if he wants to hide the dialog or not.{quote}
ok, so we will leave everything as it is. And actual changes will be only removed tabs for Mac OS.
> Remove JSF Visual/Source and Preview Tabs
> -----------------------------------------
>
> Key: JBDS-3263
> URL: https://issues.jboss.org/browse/JBDS-3263
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, visual-page-editor-core
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Fix For: 9.0.0.Beta2
>
>
> Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs.
> http://www.screencast.com/t/wettTf6s6cU
> http://www.screencast.com/t/zur1sCXmZ
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-19569:
------------------------------------------------
{quote}Then it's a bug on Mac perhaps? For me the refresh button will not take me to the first page.{quote}
And it shouldn't. On Mac and Linux you will stay on the page you was at, if you open this page in preview editor, you are likely editing code in this page. So if you refresh this page(manually or via refresh options) you likely want to see the page you were in. But on Windows we have to go to the first page, otherwise refresh will not work(known swt.ie problem). E
So I'd rather convert this issue to feature request and investigate this opportunity for beta1
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3276:
-------------------------------------
{quote}about where to put the installer i'm wonderig if we shouldn't just do it inside devstudio installer and have it as another variant of the installer ?
anything for/against that{quote}
That seems to be the best way to do it. We can download external JBDS-IS p2 repo and use assembly approach or considering JBDS Product and all deps are already in reactor we can just rebuild it again and include JBDS-IS IU's from external p2 repos.
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3276:
--------------------------------
Attachment: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png
Attached screenshot for additional step. It is fully functional, but I didn't spend any time on design just Copy-Pasted code from other steps.
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
No, there is no other way. Central does rely on p2, Eclipse does rely on p2, and p2 is shipped with EVERY Eclipse instance.
Let's not overthing that and just stick to the initial request of avoiding an error pop-up. The suggested patch does that.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
Would current approach work for installation with shared configuration that is read-only?
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
It is related to yellow marker about EA features installed and it runs every time central is opened. Is there a different way to check it without involving p2 profile?
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years