[JBoss JIRA] (JBIDE-22770) CDK server can be created without a path to cdk on second attempt
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22770?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22770.
---------------------------------
Verified in jbt 4.4.1.AM2.
> CDK server can be created without a path to cdk on second attempt
> -----------------------------------------------------------------
>
> Key: JBIDE-22770
> URL: https://issues.jboss.org/browse/JBIDE-22770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM2
>
>
> I just noticed that when I created a CDK server adapter, then deleted and they tried to create a new one, on the second page of the New Server wizard, my username was already selected (that's expected) and the Folder was empty, but I could still press Finish to create the server. And then when I went to the server editor to check if it's really empty there and it actually contains the path from my previously deleted server.
> So something is odd here.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
David Hladky commented on JBDS-3627:
------------------------------------
In other worlds the screenshot above should appear only in case you try to download the file and get 401. Otherwise you will receive a redirect to Akamai where the file can be downloaded immediately. If you instead get 401, the user should supply its user credentials (either jboss.org credentials or Red Hat account credentials (ideally the second one)). Then if the credentials are OK but the user does not have proper terms and conditions signed or there is any other error, then you receive 403 response and in Location you will receive the link user should visit in a web browser to fix the problem. When it is done, the retry attempt to download the file should pass.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM2
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
David Hladky commented on JBDS-3627:
------------------------------------
Hi, you are doing it completely wrong. The original idea behind the download plugin was it will ask the user to fill all required information and the terms and conditions will be accepted in a wizard in Eclipse (it used REST API of Download Manager to pass all required data). However [~maxandersen] insisted that it will not be done this way and the terms and conditions handling will be done in a web browser. Therefore the API was limited to just supply the basic functionality (and report it was outdated for the old versions of the Eclipse plugins).
So now when you try to download a file using JDF link (aka [https://developers.redhat.com/download-manager/jdf/file/devstudio-10.0.0....], then if the terms and conditions require additional terms and conditions to be signed, the response will be 403 and in the Location header will be suggested link the user should see in his/hers web browser. In case you do not supply the user credentials, you simply get 401 so again you should require filling credentials if such thing happens.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM2
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22591) Saving new username/pw during prompt for pw while starting cdk fails
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22591?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22591.
---------------------------------
Verified in jbt 4.4.1.AM2.
> Saving new username/pw during prompt for pw while starting cdk fails
> ---------------------------------------------------------------------
>
> Key: JBIDE-22591
> URL: https://issues.jboss.org/browse/JBIDE-22591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM1
>
>
> When the server is in a project rather than in memory, persisting changes to the server (ie changing its username) will fail because the scheduling rule for starting the server does not include the ability to modify projects. This scenario will need to be identified (is server in memory or project) and a workspace job will need to be scheduled to properly persist the changes.
> java.lang.IllegalArgumentException: Attempted to beginRule: L/Servers/Container Development Environment.server, does not match outer scope rule: Container Development Environment
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:307)
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188)
> at org.eclipse.core.internal.resources.File.setContents(File.java:334)
> at org.eclipse.core.internal.resources.File.setContents(File.java:434)
> at org.eclipse.wst.server.core.internal.Base.saveToFile(Base.java:251)
> at org.eclipse.wst.server.core.internal.Server.saveToFile(Server.java:471)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:434)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.CDKServer.getPassword(CDKServer.java:124)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:158)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22585) Selected username for CDK server adapter is ignored
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22585?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22585.
---------------------------------
Verified in jbt 4.4.1.AM2.
> Selected username for CDK server adapter is ignored
> ---------------------------------------------------
>
> Key: JBIDE-22585
> URL: https://issues.jboss.org/browse/JBIDE-22585
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM1
>
>
> When I am creating a CDK server adapter, there is combo box for username (well user and password). If I add more then 1 user and select different one then the first one, it is ignored when I am being prompted for password. The first username is preselected and there is no other way to select any other than manually type that username.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22850:
----------------------------------
Summary: createnewandnoteworthy should check versions provided
Key: JBIDE-22850
URL: https://issues.jboss.org/browse/JBIDE-22850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: website
Reporter: Jeff MAURY
The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months