[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21027.
------------------------------
I've tried it with Beta1-v20151110-2316-B137 and the EA stuff wasn't installed as expected. Closing.
> Central offers to install Early Access content when importing project examples (EA disabled)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-21027
> URL: https://issues.jboss.org/browse/JBIDE-21027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: angular.png
>
>
> 1. Open Central with EA disabled
> 2. Try to import kitchensink-angularjs project example
> 3. AngularJS (EA version) is offered to install:
> !angular.png!
> 4. Press "Download & Install".
> 5. AngularJS is installed without any warning that it's an EA content.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21070) Missing requirement bundle org.eclipse.jetty.websocket.api [9.3.2, 9.3.3)' - JBT and eclipse NEON M2
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21070?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-21070:
------------------------------------------------
[~psrna] I tried to install only feedhenry integration from nightly now(there is the same build ID as in your log) - everything was fine. I also try to install whole JBT from nightly - also no problem. Some magic happens with target platform? :)
> Missing requirement bundle org.eclipse.jetty.websocket.api [9.3.2,9.3.3)' - JBT and eclipse NEON M2
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21070
> URL: https://issues.jboss.org/browse/JBIDE-21070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Tried on eclipse neon m2 and JBT nightly (master) from 2015-11-08
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools FeedHenry Integration 1.2.0.Alpha1-v20151108-0714-B540 (org.jboss.tools.feedhenry.feature.group 1.2.0.Alpha1-v20151108-0714-B540)
> Missing requirement: BrowserSim 3.8.0.Alpha1-v20151108-0708-B257 (org.jboss.tools.browsersim.ui 3.8.0.Alpha1-v20151108-0708-B257) requires 'bundle org.eclipse.jetty.websocket.api [9.3.2,9.3.3)' but it could not be found
> Cannot satisfy dependency:
> From: Eclipse integrations of BrowserSim 3.8.0.Alpha1-v20151108-0714-B540 (org.jboss.tools.cordovasim.eclipse 3.8.0.Alpha1-v20151108-0714-B540)
> To: bundle org.jboss.tools.browsersim.ui 3.7.0
> Cannot satisfy dependency:
> From: JBoss Tools FeedHenry Integration 1.2.0.Alpha1-v20151108-0714-B540 (org.jboss.tools.feedhenry.feature.group 1.2.0.Alpha1-v20151108-0714-B540)
> To: org.jboss.tools.feedhenry.ui [1.2.0.Alpha1-v20151108-0714-B540]
> Cannot satisfy dependency:
> From: org.jboss.tools.feedhenry.ui 1.2.0.Alpha1-v20151108-0714-B540
> To: bundle org.jboss.tools.cordovasim.eclipse 3.7.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21079) Importing OpenShift 3 application via shell menu shows empty build configs table
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21079:
-------------------------------------
Attachment: no-build-configs.png
> Importing OpenShift 3 application via shell menu shows empty build configs table
> --------------------------------------------------------------------------------
>
> Key: JBIDE-21079
> URL: https://issues.jboss.org/browse/JBIDE-21079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1
>
> Attachments: no-build-configs.png
>
>
> Table in Import OpenShift Application wizard is empty when trying to import an OpenShift application via shell menu File - Import - Existing OpenShift Application. It is necessary to hit Refresh button to get any build config to the table and making it possible to import an application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21079) Importing OpenShift 3 application via shell menu shows empty build configs table
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21079:
-------------------------------------
Steps to Reproduce:
EXEC: Have an OpenShift 3 application and an existing OpenShift 3 connection for it.
EXEC: Select File - Import - Existing OpenShift Application.
EXEC: Select an existing OpenShift 3 connection (if there are no other connection, it is preselected)
EXEC: Hit Next button.
RESULT: Table listing build configs is empty.
!no-build-configs.png!
EXPECTED RESULT: There is a build config to import an OpenShift application
was:
EXEC: Have an OpenShift 3 application and an existing OpenShift 3 connection for it.
EXEC: Select File - Import - Existing OpenShift Application.
EXEC: Select an existing OpenShift 3 connection (if there are no other connection, it is preselected)
EXEC: Hit Next button.
RESULT: Table listing build configs is empty.
EXPECTED RESULT: There is a build config to import an OpenShift application
> Importing OpenShift 3 application via shell menu shows empty build configs table
> --------------------------------------------------------------------------------
>
> Key: JBIDE-21079
> URL: https://issues.jboss.org/browse/JBIDE-21079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1
>
> Attachments: no-build-configs.png
>
>
> Table in Import OpenShift Application wizard is empty when trying to import an OpenShift application via shell menu File - Import - Existing OpenShift Application. It is necessary to hit Refresh button to get any build config to the table and making it possible to import an application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21085) Connection/application wizard: reconnects if you get back and forth to the connection page
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21085:
----------------------------------------
Summary: Connection/application wizard: reconnects if you get back and forth to the connection page
Key: JBIDE-21085
URL: https://issues.jboss.org/browse/JBIDE-21085
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.3.1.Beta1
What makes this necessary is the internal behaviour of the connection page being used when application- or import-wizard are launched from central or file-menu. It there is a delegating wizard page which invokes either v2 or v3 wizard based on the server type that the user is choosing. Behind the scenes I see the conn wizard connecting several times when launched from central/file-menu. The delegating wizard page needs to connect in the WizardPage#getNextPage(), a method that is also used in PageChangingListener(s) which it's using to determine the page change direction (forward or backward).
how to reproduce:
# EXEC: launch application wizard
# ASSERT: connection page shows up
# EXEC: select an existing or create a new connection
# EXEC: get to the next page
# EXEC: get back to the connection page and hit "Next" again
Result:
You see the progress bar coming up and getting to the 2nd page again after some delay caused by the the wizard re-connecting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21085) Connection/application wizard: reconnects if you get back and forth to the connection page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21085?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21085:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Connection/application wizard: reconnects if you get back and forth to the connection page
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21085
> URL: https://issues.jboss.org/browse/JBIDE-21085
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> What makes this necessary is the internal behaviour of the connection page being used when application- or import-wizard are launched from central or file-menu. It there is a delegating wizard page which invokes either v2 or v3 wizard based on the server type that the user is choosing. Behind the scenes I see the conn wizard connecting several times when launched from central/file-menu. The delegating wizard page needs to connect in the WizardPage#getNextPage(), a method that is also used in PageChangingListener(s) which it's using to determine the page change direction (forward or backward).
> how to reproduce:
> # EXEC: launch application wizard
> # ASSERT: connection page shows up
> # EXEC: select an existing or create a new connection
> # EXEC: get to the next page
> # EXEC: get back to the connection page and hit "Next" again
> Result:
> You see the progress bar coming up and getting to the 2nd page again after some delay caused by the the wizard re-connecting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21085) Connection/application wizard: reconnects if you get back and forth to the connection page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21085?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21085:
-------------------------------------
Fix Version/s: (was: 4.3.1.Beta1)
> Connection/application wizard: reconnects if you get back and forth to the connection page
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21085
> URL: https://issues.jboss.org/browse/JBIDE-21085
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> What makes this necessary is the internal behaviour of the connection page being used when application- or import-wizard are launched from central or file-menu. It there is a delegating wizard page which invokes either v2 or v3 wizard based on the server type that the user is choosing. Behind the scenes I see the conn wizard connecting several times when launched from central/file-menu. The delegating wizard page needs to connect in the WizardPage#getNextPage(), a method that is also used in PageChangingListener(s) which it's using to determine the page change direction (forward or backward).
> how to reproduce:
> # EXEC: launch application wizard
> # ASSERT: connection page shows up
> # EXEC: select an existing or create a new connection
> # EXEC: get to the next page
> # EXEC: get back to the connection page and hit "Next" again
> Result:
> You see the progress bar coming up and getting to the 2nd page again after some delay caused by the the wizard re-connecting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months