June 2015 - jbosstools-issues - Jboss List Archives

[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 looked into Eclipse preferences and I see that krb5 is in 1st place by default. You can switch the ordering. I bet that you can avoid the krb5 prompt if you move it further down, away from the 1st priority: !krb5-auth-method-is-1st.png! Can you confirm this? > 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, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.x > > Attachments: authorized.png, creds_prompt.png, jstack.txt, krb5-auth-method-is-1st.png > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. 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

1
0
0 / 0

[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 updated JBIDE-19971: ------------------------------------- Attachment: krb5-auth-method-is-1st.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, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.x > > Attachments: authorized.png, creds_prompt.png, jstack.txt, krb5-auth-method-is-1st.png > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19968: ------------------------------------------ [~fbricon]: can you please review my 2-liner PR for branch at https://github.com/jbosstools/jbosstools-openshift/pull/659? > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta1 > > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19968: ------------------------------------- Affects Version/s: 4.3.0.Beta1 > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta1 > > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20009) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20009?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20009: ------------------------------------- Affects Version/s: 4.3.0.Beta1 > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20009 > URL: https://issues.jboss.org/browse/JBIDE-20009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: import-showing-label-not-key.png, Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19968: ---------------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta1 > > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19945) org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19945?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19945. ------------------------------- It seems to be working with a proper configuration, so I'll just close this. > org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures > --------------------------------------------------------------------------- > > Key: JBIDE-19945 > URL: https://issues.jboss.org/browse/JBIDE-19945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite > ------------------------------------------------------------------------------- > Tests run: 7, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 22.278 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite > testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 0.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: The JRE5 location is not right > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69) > at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.setUp(JBossWSTopDownCommandTest.java:59) > testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 0.508 sec <<< ERROR! > java.lang.NullPointerException: null > at org.eclipse.jdt.launching.AbstractVMInstall.setName(AbstractVMInstall.java:120) > at org.jboss.tools.as.test.core.internal.utils.JREUtils.createJRE(JREUtils.java:104) > at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.setUp(JBossWSJavaFirstCommandTest.java:64) > testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE! > junit.framework.AssertionFailedError: The JRE5 location is not right > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69) > at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48) > testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0.001 sec <<< FAILURE! > junit.framework.AssertionFailedError: The JRE5 location is not right > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69) > at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48) > testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE! > junit.framework.AssertionFailedError: The JRE5 location is not right > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69) > at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48) > testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 16.904 sec > testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 4.789 sec > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19645. ------------------------------- I'll close this one then. > Remove seam 3 features from JBDS, JBT default install; add new connector to Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-19645 > URL: https://issues.jboss.org/browse/JBIDE-19645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions, central, updatesite > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png > > > Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2: > * remove from CoreTools categories on update sites > * remove from JBDS core.feature > * create new connectors in JBT and JBDS Central > [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20013) Update Eclipse Docker Tooling in the Target Platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20013?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20013: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Update Eclipse Docker Tooling in the Target Platforms > ----------------------------------------------------- > > Key: JBIDE-20013 > URL: https://issues.jboss.org/browse/JBIDE-20013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Labels: respin-a > Fix For: 4.3.0.Beta1 > > > Please update the Docker tooling to the latest version in our TP, since we included numerous bug fixes since JBIDE-19848. > The current version for the Docker tooling is 1.0.0.201506100402 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20013) Update Eclipse Docker Tooling in the Target Platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20013?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20013: ----------------------------------- Labels: respin-a (was: ) > Update Eclipse Docker Tooling in the Target Platforms > ----------------------------------------------------- > > Key: JBIDE-20013 > URL: https://issues.jboss.org/browse/JBIDE-20013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Labels: respin-a > Fix For: 4.3.0.Beta1 > > > Please update the Docker tooling to the latest version in our TP, since we included numerous bug fixes since JBIDE-19848. > The current version for the Docker tooling is 1.0.0.201506100402 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015