June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2199) remove obsolete PDE build stuff from devstudio SVN tree

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2199: -------------------------------- Summary: remove obsolete PDE build stuff from devstudio SVN tree Key: JBDS-2199 URL: https://issues.jboss.org/browse/JBDS-2199 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 6.0.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 6.0.0.M1 The following folders are deprecated and should be removed: devstudio-installer transforms releng -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-11663) Both nightly-staging-composite and staging-aggregate profiles activated automatically for swtbot tests

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11663: --------------------------------------- Summary: Both nightly-staging-composite and staging-aggregate profiles activated automatically for swtbot tests Key: JBIDE-11663 URL: https://issues.jboss.org/browse/JBIDE-11663 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Lucia Jelinkova Assignee: Nick Boldt Fix For: 3.3.0.Beta3 With addition of staging-aggregate profiles there are 4 profiles activated by default when swtbot.test.skip property is set to "false" (as is used for all swtbot tests). As a result, both the nightly and aggregation repositories are added for resolving target platform. {code} [INFO] Adding repository http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S... [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli... [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ {code} Please, remove automatic activation of those profiles when swtbot.test.skip=false. QE would prefer to specify those profiles on the command line. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
15
0 / 0

[JBoss JIRA] (JBIDE-12005) Handle SSH auth fail correctly

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12005: ------------------------------------- Summary: Handle SSH auth fail correctly Key: JBIDE-12005 URL: https://issues.jboss.org/browse/JBIDE-12005 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 Trying to open PortForwarding with no valid ssh key gives the following error: !ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-05-25 12:18:11.339 !MESSAGE Could not load forwardable ports for application 'chat' !STACK 0 com.openshift.client.OpenShiftSSHOperationException: Failed to open a new SSH session for application 'chat' at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardModel.verifyApplicationSSHSession(ApplicationPortForwardingWizardModel.java:224) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage$12.run(ApplicationPortForwardingWizardPage.java:333) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: com.jcraft.jsch.JSchException: Auth fail at com.jcraft.jsch.Session.connect(Session.java:461) at com.jcraft.jsch.Session.connect(Session.java:154) at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:106) at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:83) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardModel.verifyApplicationSSHSession(ApplicationPortForwardingWizardModel.java:220) ... 2 more !ENTRY org.eclipse.core.databinding 4 0 2012-05-25 12:18:12.051 !MESSAGE Unhandled exception: com.openshift.client.OpenShiftSSHOperationException: No SSH session available for application 'chat' !STACK 0 java.lang.RuntimeException: com.openshift.client.OpenShiftSSHOperationException: No SSH session available for application 'chat' at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:65) at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:51) at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:83) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:104) at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:55) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:103) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:103) at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:486) at org.eclipse.core.databinding.ValueBinding$4.run(ValueBinding.java:197) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:188) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:151) at org.eclipse.core.databinding.ValueBinding.updateTargetToModel(ValueBinding.java:112) at org.eclipse.core.databinding.DataBindingContext.updateModels(DataBindingContext.java:451) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:175) at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:168) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage.onPageActivated(ApplicationPortForwardingWizardPage.java:327) at org.jboss.tools.openshift.express.internal.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:76) at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1554) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1552) at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1337) at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1289) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:610) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingAction.run(ApplicationPortForwardingAction.java:32) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) Caused by: com.openshift.client.OpenShiftSSHOperationException: No SSH session available for application 'chat' at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:582) at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:559) at com.openshift.internal.client.ApplicationResource.getForwardablePorts(ApplicationResource.java:532) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardModel.updateLocalAddressBindings(ApplicationPortForwardingWizardModel.java:161) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardModel.setUseDefaultLocalIpAddress(ApplicationPortForwardingWizardModel.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59) ... 68 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11810) OpenShift port forwarding exception without ssh key

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11810: -------------------------------------- Summary: OpenShift port forwarding exception without ssh key Key: JBIDE-11810 URL: https://issues.jboss.org/browse/JBIDE-11810 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.CR1 Attachments: machydraerrorportdialog.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
8
0 / 0

[JBoss JIRA] (JBIDE-12018) first time I open Port forwarding on an app it pops up the dialog and closes it again instantly

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12018: ------------------------------------------- Summary: first time I open Port forwarding on an app it pops up the dialog and closes it again instantly Key: JBIDE-12018 URL: https://issues.jboss.org/browse/JBIDE-12018 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Max Rydahl Andersen Assignee: Xavier Coulon Priority: Critical Fix For: 3.3.0.CR1 see title. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
17
0 / 0

[JBoss JIRA] (JBIDE-11535) OpenShift use case : Can create application without ssh key

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11535: -------------------------------------- Summary: OpenShift use case : Can create application without ssh key Key: JBIDE-11535 URL: https://issues.jboss.org/browse/JBIDE-11535 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta2 Environment: Windows 7 JBDS 5.0.0.Beta2 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Blocker Fix For: 3.3.0.CR1 During JBQA-6232 verification I wanted to test this scenario on windows but forgot that I do not have my ssh keys on the windows machine. Despite this fact I was able to create a new application on OpneShift! but the wizard wasn't able to look up the newly created application (even when I was able to reach it via my browser). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
17
0 / 0

[JBoss JIRA] (JBIDE-12117) Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12117: --------------------------------------- Summary: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed Key: JBIDE-12117 URL: https://issues.jboss.org/browse/JBIDE-12117 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Priority: Minor Fix For: 3.4.x Attachments: eclipse.jpg In Openshift Explorer, when I invoke the Port forwarding menu item, the Verifying SSH session job's dialog is displayed and won't close until the Port forwarding dialog is closed. !eclipse.jpg! Could it be changed so that when the job is finished the dialog is closed and Port forwarding dialog is shown? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-11651) Issues when importing TicketMonster

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11651: ---------------------------------------- Summary: Issues when importing TicketMonster Key: JBIDE-11651 URL: https://issues.jboss.org/browse/JBIDE-11651 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta3 Reporter: Marius Bogoevici Assignee: Fred Bricon While importing TicketMonster (https://github.com/jboss/ticket-monster/tree/errai-merged - 'errai-merged' branch is important for GWT issues), there are a number of issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
11
0 / 0

[JBoss JIRA] (JBIDE-12066) Unable to create Maven archetype project from Nexus Indexer

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-12066: ---------------------------------------- Summary: Unable to create Maven archetype project from Nexus Indexer Key: JBIDE-12066 URL: https://issues.jboss.org/browse/JBIDE-12066 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Rastislav Wagner Assignee: Fred Bricon Priority: Blocker Fix For: 3.3.0.CR1 org.eclipse.core.runtime.CoreException: Could not resolve artifact jboss.maven-archetypes:jboss-archetype-simple:pom:1.0 at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:658) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:625) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:536) at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:241) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:45) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:49) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: Missing jboss.maven-archetypes:jboss-archetype-simple:pom:1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] (JBDS-1878) Find a way to set up / install EAP6/WFK repos (automatically)

by Fred Bricon (Created) (JIRA)

Find a way to set up / install EAP6/WFK repos (automatically) ------------------------------------------------------------- Key: JBDS-1878 URL: https://issues.jboss.org/browse/JBDS-1878 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: installer, maven Affects Versions: 5.0.0.M2 Reporter: Fred Bricon Fix For: 5.0.0.CR1 We need to find a way to let users easily use the EAP6 / WFK maven repos. Basically, it boils down to 2 use cases : 1 - The user wants to use the repos from his enterprise repository manager 2 - The user wants to install the repos locally Installation / configuration of the repos can be done either via the JBDS installer (Burr's idea) or a JBDS plugin (Max's idea). 1 - If the user chooses to use a remote repo, then may be open a page detailing the required steps to install EAP6/WFK on nexus/artifactory/archiva. I'm not sure this would be necessary since Joe developper will probably won't have the rights to manage his enterprise repo management app. So we might as well bail and assume he has everything configured. 2 - The user chooses to install the repos locally. We can detect if the repos are already configured before continuing : Check if one remote repository already contains specific jars only available in EAP6/WFK repos or look for a specific snippet in the user / global settingsea. - if nothing is found, unzip and either ask the user to change his settings manually (showing him the right xml snippet) or do it automatically for him (by adding a new profile activated by default) Question is : where are the repos coming from? will they be publicly available, i.e. easily downloadable? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
7
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 2012