August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22712) NullPointerException in GettingStartedHtmlPage.updateEarlyAccess

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22712?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22712. --------------------------------- Closing. AERI problem should be reopened automatically if this keeps occurring in future versions. > NullPointerException in GettingStartedHtmlPage.updateEarlyAccess > ---------------------------------------------------------------- > > Key: JBIDE-22712 > URL: https://issues.jboss.org/browse/JBIDE-22712 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:367) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:350) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:335) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > {noformat} > Bundles: > | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.Alpha1-v20160623-1622-B929 | > Operating Systems: > | Linux | 2.6.32.22 | 4.4.11.fc22 | > | MacOSX | 10.10.5 | 10.11.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5715ca22e4b055563f...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22710) NullPointerException in JBossCentralActivator.openJBossCentralEditor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22710?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22710. --------------------------------- Yeah, it's hard to verify these. But if the aeri problem is set up correctly, it should have a version of a bundle where this is fixed. And if this problem happens again in newer versions, the problem should be reopened automatically. > NullPointerException in JBossCentralActivator.openJBossCentralEditor > -------------------------------------------------------------------- > > Key: JBIDE-22710 > URL: https://issues.jboss.org/browse/JBIDE-22710 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:435) > at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:386) > at org.jboss.tools.central.actions.ShowJBossCentralHandler.execute(ShowJBossCentralHandler.java:29) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.Final-v20160613-2000-B8 | > Operating Systems: > | Linux | 3.13.0 | 4.4.9.fc23 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571e5eaee4b08bd809...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22653: ------------------------------------------ [~fbricon] [~jeffmaury] I cant replicate this. I can scale down to 0 and back again to some other number. I see in both cases the pods being terminated & removed and relaunched again. The only missing piece I can spot is that the refresh wont happen automatically. If you refresh manually you see the changes happening: https://youtu.be/RGiibHCgaeA > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17615) When runtime download asks to reenter credentials, it will not accept them even if valid

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17615: ---------------------------------- Attachment: reenter-password.png > When runtime download asks to reenter credentials, it will not accept them even if valid > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17615 > URL: https://issues.jboss.org/browse/JBIDE-17615 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2c B130 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: reenter-password.png > > > I was playing around JBIDE-17601 - that JIRA is about the bug that JBoss.org credentials were not validated when you went through new archetype from central -> Download & Install. So you could enter anything and it would let you carry on. But once the real download is about to start, you will get a popup to enter the credentials again (since the downloader needs the correct password). Even if you now enter the correct credentials, it will ask you 2 more times and then fail on Incorrect password. > Yes, this will be less likely to happen once JBIDE-17601 is fixed. But I suppose that the popup is in place exactly for the situation when the password needs to be corrected, so it should work, right? > There may still be a valid use case to hit this issue (although a very rare case): > 1. User starts the runtime download dialog, enters correct credentials, moves to license > 2. User changes his password on jboss.org > 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials > So in my opinion, if we already have a mechanism to ask for credentials again, then it should work. If you say this is not needed, then why even allow the popup? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17615) When runtime download asks to reenter credentials, it will not accept them even if valid

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-17615 at 8/2/16 7:28 AM: --------------------------------------------------------------- I was waiting for jboss.org change password page to be fixed to verify this: ORG-3476 But today I realized that I can use a Red Hat Developer account instead. So I used a new social account that I created at developers.redhat.com using my github account. I was able to download EAP normally - that verified JBIDE-21801 is fixed. But then I tried the scenario when I first go through the dialog and after entering the credentials in Eclipse and just before the actual download starts, I changed my rh developer password. I got a pop up asking me for credentials. !reenter-password.png! But now I was unable to make it work even if I provided the new password. (And when I finally cancelled this and went through the dialog again, I was able to download using the new password.) Note that it's not clear from this dialog what domain I'm using, but I assume it should use the same domain that I used originally. I would argue that the account name should probably be locked down as well at this point. was (Author: mmalina): I was waiting for jboss.org change password page to be fixed to verify this: ORG-3476 But today I realized that I can use a Red Hat Developer account instead. So I used a new social account that I created at developers.redhat.com using my github account. I was able to download EAP normally - that verified JBIDE-21801 is fixed. But then I tried the scenario when I first go through the dialog and after entering the credentials in Eclipse and just before the actual download starts, I changed my rh developer password. I got a pop up asking me for credentials. But now I was unable to make it work even if I provided the new password. (And when I finally cancelled this and went through the dialog again, I was able to download using the new password.) Note that it's not clear from this dialog what domain I'm using, but I assume it should use the same domain that I used originally. I would argue that the account name should probably be locked down as well at this point. > When runtime download asks to reenter credentials, it will not accept them even if valid > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17615 > URL: https://issues.jboss.org/browse/JBIDE-17615 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2c B130 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: reenter-password.png > > > I was playing around JBIDE-17601 - that JIRA is about the bug that JBoss.org credentials were not validated when you went through new archetype from central -> Download & Install. So you could enter anything and it would let you carry on. But once the real download is about to start, you will get a popup to enter the credentials again (since the downloader needs the correct password). Even if you now enter the correct credentials, it will ask you 2 more times and then fail on Incorrect password. > Yes, this will be less likely to happen once JBIDE-17601 is fixed. But I suppose that the popup is in place exactly for the situation when the password needs to be corrected, so it should work, right? > There may still be a valid use case to hit this issue (although a very rare case): > 1. User starts the runtime download dialog, enters correct credentials, moves to license > 2. User changes his password on jboss.org > 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials > So in my opinion, if we already have a mechanism to ask for credentials again, then it should work. If you say this is not needed, then why even allow the popup? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17615) When runtime download asks to reenter credentials, it will not accept them even if valid

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17615: ---------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > When runtime download asks to reenter credentials, it will not accept them even if valid > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17615 > URL: https://issues.jboss.org/browse/JBIDE-17615 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2c B130 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: reenter-password.png > > > I was playing around JBIDE-17601 - that JIRA is about the bug that JBoss.org credentials were not validated when you went through new archetype from central -> Download & Install. So you could enter anything and it would let you carry on. But once the real download is about to start, you will get a popup to enter the credentials again (since the downloader needs the correct password). Even if you now enter the correct credentials, it will ask you 2 more times and then fail on Incorrect password. > Yes, this will be less likely to happen once JBIDE-17601 is fixed. But I suppose that the popup is in place exactly for the situation when the password needs to be corrected, so it should work, right? > There may still be a valid use case to hit this issue (although a very rare case): > 1. User starts the runtime download dialog, enters correct credentials, moves to license > 2. User changes his password on jboss.org > 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials > So in my opinion, if we already have a mechanism to ask for credentials again, then it should work. If you say this is not needed, then why even allow the popup? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21801) Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21801: --------------------------------------- I verified this in JBT 4.4.1.AM2. > Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup > ----------------------------------------------------------------------------- > > Key: JBIDE-21801 > URL: https://issues.jboss.org/browse/JBIDE-21801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png > > > first technical investigation: > - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%... > and it returns: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <result> > <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText> > <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText> > <customParams> > <param name="company" label="Company" /> > <param name="country" label="Country" > > <options multiple="false"> > </options> > </param> > <param name="downloadURL" label="Downloaded file" > > <options multiple="false"> > <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/> > </options> > </param> > </customParams> > </result> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21801) Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21801. --------------------------------- This works for me as well. I created an account at developers.redhat.com using my github account and email using a +github suffix. Then I was able to download EAP 7 in eclipse using account mmalina-github and the password I set up. > Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup > ----------------------------------------------------------------------------- > > Key: JBIDE-21801 > URL: https://issues.jboss.org/browse/JBIDE-21801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png > > > first technical investigation: > - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%... > and it returns: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <result> > <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText> > <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText> > <customParams> > <param name="company" label="Company" /> > <param name="country" label="Country" > > <options multiple="false"> > </options> > </param> > <param name="downloadURL" label="Downloaded file" > > <options multiple="false"> > <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/> > </options> > </param> > </customParams> > </result> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in Base root pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19081. --------------------------------- I think this can be safely closed - there is a followup jira. > Use simpler Surefire include/exclude pattern in Base root pom > ------------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22835) Freemarker New and Noteworthy for 4.4.1.AM2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22835?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22835. --------------------------------- > Freemarker New and Noteworthy for 4.4.1.AM2 > ------------------------------------------- > > Key: JBIDE-22835 > URL: https://issues.jboss.org/browse/JBIDE-22835 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016