[JBoss JIRA] (JBIDE-19970) Unable to download products (EAP, ...)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19970?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19970:
--------------------------------
Priority: Blocker (was: Critical)
> Unable to download products (EAP, ...)
> --------------------------------------
>
> Key: JBIDE-19970
> URL: https://issues.jboss.org/browse/JBIDE-19970
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
> Priority: Blocker
>
> It's impossible to download products via download runtime wizard.
> It tries to download it but after few seconds error dialog just flashes and no error in error log is recorded.
> After capturing the process on video and pausing it when the error dialog pops up, I figured it says that the downloaded file is not properly formated zip file.
> The file it downloads just contains html page:
> {noformat:title=➜ ~ cat temp/jboss-eap-6.4.0.GA.zip }
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> "http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
> <title>JBoss Community</title>
> <style type="text/css">
> body {
> margin: 230px 0 0 0;
> text-align: center;
> font-family: 'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
> font-size:15px;
> background: #e6e7e8 url(http://design.jboss.org/jbossorg/code/jbossorg_3_0/images/errorbkg.png) no-repeat top center;
> }
> .wrappper {
> width:600px;
> margin: auto;
> text-align: left;
> line-height: 20px;
> }
> h2 {
> color:#424242;
> display:block;
> font-family:Myriad Pro,Helvetica,Arial,sans-serif;
> font-size:25px;
> font-weight:normal;
> letter-spacing:-0.03em;
> margin-top:5px;
> }
> </style>
> </head>
> <body>
> <div class="wrappper" >
> <h2>Cookies disabled</h2>
> <p>The download requires cookies to be enabled in your web browser.</p>
> <p>Please, enable cookies and reload the page.</p>
> </div>
> </body>
> </html>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-19971:
---------------------------------------
jstack output attached, it was taken in the point when kerberos user name prompt was shown.
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: authorized.png, creds_prompt.png, jstack.txt
>
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19971:
----------------------------------
Attachment: jstack.txt
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: authorized.png, creds_prompt.png, jstack.txt
>
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19970) Unable to download products (EAP, ...)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19970?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19970:
-------------------------------------
I've replicated the issue. I'll be opening a ORG bug ASAP
> Unable to download products (EAP, ...)
> --------------------------------------
>
> Key: JBIDE-19970
> URL: https://issues.jboss.org/browse/JBIDE-19970
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
> Priority: Critical
>
> It's impossible to download products via download runtime wizard.
> It tries to download it but after few seconds error dialog just flashes and no error in error log is recorded.
> After capturing the process on video and pausing it when the error dialog pops up, I figured it says that the downloaded file is not properly formated zip file.
> The file it downloads just contains html page:
> {noformat:title=➜ ~ cat temp/jboss-eap-6.4.0.GA.zip }
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> "http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
> <title>JBoss Community</title>
> <style type="text/css">
> body {
> margin: 230px 0 0 0;
> text-align: center;
> font-family: 'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
> font-size:15px;
> background: #e6e7e8 url(http://design.jboss.org/jbossorg/code/jbossorg_3_0/images/errorbkg.png) no-repeat top center;
> }
> .wrappper {
> width:600px;
> margin: auto;
> text-align: left;
> line-height: 20px;
> }
> h2 {
> color:#424242;
> display:block;
> font-family:Myriad Pro,Helvetica,Arial,sans-serif;
> font-size:25px;
> font-weight:normal;
> letter-spacing:-0.03em;
> margin-top:5px;
> }
> </style>
> </head>
> <body>
> <div class="wrappper" >
> <h2>Cookies disabled</h2>
> <p>The download requires cookies to be enabled in your web browser.</p>
> <p>Please, enable cookies and reload the page.</p>
> </div>
> </body>
> </html>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19976) Search for quickstarts in Central is not consistent
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19976?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19976:
-----------------------------------
Assignee: Fred Bricon
> Search for quickstarts in Central is not consistent
> ---------------------------------------------------
>
> Key: JBIDE-19976
> URL: https://issues.jboss.org/browse/JBIDE-19976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Environment: Windows 8.1, Fedora 22
> Reporter: Radim Hopp
> Assignee: Fred Bricon
>
> Most of the time, the the results provided by search do not have labels.
> Once Central is opened, it returns the same results, but sometimes when you close&reopen central it cannot find quickstarts it could found previously and vice versa.
> For example right now, I have two instances of JBT/JBDS openew with central and searching for "greeter" in one results in no quickstarts found and in the second one finds just one quickstart - "jboss-greeter". After closing and reopening Central in the instance, which previously has shown "jboss-greeter", when seached for "greeter", now it finds some another quickstart named "greeter".
> I couldn't find any determinism in this behaviour.
> I can see no errors in error log, nor any error dialog.
> Sometimes, when I click on the found quickstart, new quickstart wizard is shown, sometimes nothing happens (again, no error anywhere).
> I have tried it on JBT 4.3.0.Beta1 on Fedora 22 with GTK3/GTK2, JBDS 9.0.0.Beta1 on Fedora 22 with GTK2/3 and on Windows 8.1 on JBDS 9.0.0.Beta1.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19971:
------------------------------------------
[~mlabuda] Could we please have some other QE member trying to reproduce this, too?
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: authorized.png, creds_prompt.png
>
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-19919.
------------------------------------
Resolution: Done
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-19919
> URL: https://issues.jboss.org/browse/JBIDE-19919
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19919.
----------------------------------
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-19919
> URL: https://issues.jboss.org/browse/JBIDE-19919
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
){kind=link}