[JBoss JIRA] (JBIDE-19591) Explorer: connection is not refreshed if I edit it and change the host
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19591?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19591:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have a connection in the explorer
# EXEC: edit your connection and change the host and hit "Finish"
Result:
The explorer should show the new url for the connection that we just edited.
Expected Result:
Once back in the explorer (connection wizard closed), the connection should reflect the new server
was:
# ASSERT: make sure that you have a connection in the explorer
# EXEC: edit your connection and change the host and hit "Finish"
Result:
Once back in the explorer (connection wizard closed), the connection should reflect the new server
> Explorer: connection is not refreshed if I edit it and change the host
> ----------------------------------------------------------------------
>
> Key: JBIDE-19591
> URL: https://issues.jboss.org/browse/JBIDE-19591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.0.Beta2
>
>
--
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 commented on JBIDE-19919:
----------------------------------------
[~nickboldt], done - https://github.com/jbosstools/jbosstools-base/commit/49f7ff25ba3ab511c985...
Sorry for the delay.
> 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-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] I have absolutely no clue how this is even possible. Is it possible for you to get a stack-trace of JBDS while you are at this prompt, ex. via jstack?
> 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-19961) org.jboss.tools.common.core.test.WebUtilsTest failure on Windows
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19961?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19961:
----------------------------------
Fix Version/s: 4.3.0.Beta2
> org.jboss.tools.common.core.test.WebUtilsTest failure on Windows
> ----------------------------------------------------------------
>
> Key: JBIDE-19961
> URL: https://issues.jboss.org/browse/JBIDE-19961
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Environment: Windows 8.1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.common.core.test.CommonCoreTestSuite
> -------------------------------------------------------------------------------
> Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 16.24 sec <<< FAILURE! - in org.jboss.tools.common.core.test.CommonCoreTestSuite
> testGetWebContentPaths(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 9.101 sec
> testGeWebRootFolders(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.293 sec
> testFindResource(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 0.889 sec <<< FAILURE!
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.tools.common.core.test.WebUtilsTest.testFindResource(WebUtilsTest.java:205)
> testFirstWebContentPath(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.17 sec
> testGetWebPath(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 0.872 sec
> testGetWebRootFolder(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.119 sec
> testCreateHttpURLConnection(org.jboss.tools.common.core.test.HttpUtilTest) Time elapsed: 0.03 sec
> testInputStreamReader(org.jboss.tools.common.core.test.HttpUtilTest) Time elapsed: 0.917 sec
> testDefaultBeanName(org.jboss.tools.common.core.test.BeanUtilTest) Time elapsed: 0.001 sec
> testSubtypesInJar(org.jboss.tools.common.core.test.JandexTest) Time elapsed: 0.57 sec
> testAnnotationInJar(org.jboss.tools.common.core.test.JandexTest) Time elapsed: 0.233 sec
> {code}
--
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 edited comment on JBIDE-19976 at 6/8/15 12:09 PM:
--------------------------------------------------------------
the example indexing seems to have changed. I've updated the search query url to http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont...
New behavior I can see :
* EAP 6.3.0 artifacts are no longer retrieved
* some new DATAGRID-JBOSS_AS_QUICKSTARTS_3-24-G7BE4B6D tagged examples show up. That tag is dynamically added by us by expecting some conventions to be followed by the examples (product + git_tag_matching_product_version), but it looks bad in that case
Anyways, please close and reopen Eclipse/JBDS to see the change
was (Author: fbricon):
the example indexing seems to have changed. I've updated the search query url to http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont...
New behavior I can see :
* EAP 6.3.0 artifacts are no longer retrieved
* some new DATAGRID-JBOSS_AS_QUICKSTARTS_3-24-G7BE4B6D tagged examples show up. That tag is dynamically added by us by expecting some conventions to be followed by the examples (product + git_tag_matching_product_version), but it looks bad in that case
> 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
>
> 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-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 commented on JBIDE-19976:
-------------------------------------
the example indexing seems to have changed. I've updated the search query url to http://dcp.jboss.org/v1/rest/search?content_provider=jboss-developer&cont...
New behavior I can see :
* EAP 6.3.0 artifacts are no longer retrieved
* some new DATAGRID-JBOSS_AS_QUICKSTARTS_3-24-G7BE4B6D tagged examples show up. That tag is dynamically added by us by expecting some conventions to be followed by the examples (product + git_tag_matching_product_version), but it looks bad in that case
> 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
>
> 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 Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-19971:
---------------------------------------
Right after Host key acceptance dialog is shown and host key is accepted, the clone of remote git repo hangs and the prompt is shown in command line
!creds_prompt.png!
when credentials are filled in then clone finish successfully
!authorized.png!
> 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-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: creds_prompt.png
authorized.png
> 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