[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23031:
-----------------------------------
Fix Version/s: 4.4.1.Final
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22795) Create integration tests PR check job for openshift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22795?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22795 at 8/23/16 8:57 AM:
----------------------------------------------------------------
Job is created but it is blocked bcs nested virtualization is still not working on CI and usage of remote server would require personal credentials which are not possible to pass in automatized PR checker. Thus leaving open until it get solved.
was (Author: mlabuda):
Blocked bcs nested virtualization is still not working on CI and usage of remote server would require personal credentials which are not possible to pass in automatized PR checker.
> Create integration tests PR check job for openshift
> ---------------------------------------------------
>
> Key: JBIDE-22795
> URL: https://issues.jboss.org/browse/JBIDE-22795
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Rastislav Wagner
> Assignee: Marián Labuda
> Fix For: 4.4.x
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-842) Improve the stability of SwitchYard debugger tests
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-842:
---------------------------------------
Summary: Improve the stability of SwitchYard debugger tests
Key: JBTIS-842
URL: https://issues.jboss.org/browse/JBTIS-842
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, switchyard
Affects Versions: 4.3.1.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.3.1.Final
It seems that the Breakpoints view sometimes disable the button 'Remove All Breakpoints' even if there is at least one breakpoint. The stacktrace is as follows
{code}
org.jboss.reddeer.swt.exception.SWTLayerException: SWT Shell passed to constructor is null. The following shells are available
class org.eclipse.swt.widgets.Shell with text 'Debug - org.switchyard.handlers.ValidateHandler - JBoss Developer Studio'
at org.jboss.reddeer.swt.impl.shell.AbstractShell.<init>(AbstractShell.java:34)
at org.jboss.reddeer.swt.impl.shell.DefaultShell.<init>(DefaultShell.java:24)
at org.jboss.tools.switchyard.reddeer.debug.BreakpointsView.removeAllBreakpoints(BreakpointsView.java:47)
at org.jboss.tools.switchyard.ui.bot.test.DebuggerDebuggingTest.removeAllBreakpoints(DebuggerDebuggingTest.java:86)
{code}
To workaround this just close and reopen the Breakpoints view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-402) Add commands in Image Hierarchy view [EBZ#499750]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-402:
---------------------------------------
Summary: Add commands in Image Hierarchy view [EBZ#499750]
Key: ERT-402
URL: https://issues.jboss.org/browse/ERT-402
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
The Docker Image Hierarchy view does not provide any command yet. We should at least propose to:
- refresh the treeview
- delete images
- run images
- show in properties view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23029:
------------------------------------------
a great way it seems, to get a requirement fullfilled (without erroring - ex. test needs a connection) would be to provide an annotiation like the requirement assertion @RunIf. Something like @Requires or @Needs could fit well.
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22963?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22963:
---------------------------------------
Just wanted to report that it's still there in devstudio-10.1.0.GA-v20160823-0457-B5835-installer-standalone.jar . I know it hasn't been fixed yet, just bumping it a little bit ;)
> NPE when creating a html5 project
> ---------------------------------
>
> Key: JBIDE-22963
> URL: https://issues.jboss.org/browse/JBIDE-22963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> I get this NPE when I create the HTML5 project from Central:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
> at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
> at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:758)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23035) Support WildFly 10.1 - change server adapter name
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23035?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23035:
----------------------------------
Description:
WildFly 10.1 has been released.
We need to make sure it works properly.
My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1.
AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
was:
WildFly 10.1 has been released.
We need to make sure it works properly.
My initial test doesn't show any problems. AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
> Support WildFly 10.1 - change server adapter name
> -------------------------------------------------
>
> Key: JBIDE-23035
> URL: https://issues.jboss.org/browse/JBIDE-23035
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> WildFly 10.1 has been released.
> We need to make sure it works properly.
> My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1.
> AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23035) Support WildFly 10.1 - change server adapter name
by Martin Malina (JIRA)
Martin Malina created JBIDE-23035:
-------------------------------------
Summary: Support WildFly 10.1 - change server adapter name
Key: JBIDE-23035
URL: https://issues.jboss.org/browse/JBIDE-23035
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.4.1.AM3
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.4.1.Final
WildFly 10.1 has been released.
We need to make sure it works properly.
My initial test doesn't show any problems. AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22856) TP does not allow to run RedDeer UI tests
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22856?page=com.atlassian.jira.plugi... ]
Jeff MAURY resolved JBIDE-22856.
--------------------------------
Resolution: Duplicate Issue
> TP does not allow to run RedDeer UI tests
> -----------------------------------------
>
> Key: JBIDE-22856
> URL: https://issues.jboss.org/browse/JBIDE-22856
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Fix For: 4.4.1.Final
>
>
> The TP does not allow to run RedDeer UI tests. When launching such a test, the following error is shown:
> {code:shell}
> !ENTRY org.eclipse.osgi 4 0 2016-07-29 16:46:32.581
> !MESSAGE Application error
> !STACK 1
> java.lang.RuntimeException: Application "org.jboss.reddeer.ui.reddeertestapplication" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.ant.ui.antRunner, org.eclipse.datatools.connectivity.console.profile.StorageFileEditor, org.eclipse.e4.ui.workbench.swt.E4Application, org.eclipse.e4.ui.workbench.swt.GenTopic, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.jdt.core.JavaIndexer, org.eclipse.pde.build.Build, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.legacytestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication, org.eclipse.swtbot.eclipse.core.swtbottestapplication, org.eclipse.ui.ide.workbench, org.eclipse.wst.jsdt.core.JavaCodeFormatter, org.eclipse.wst.server.preview.preview, org.eclipse.xsd.ecore.importer.XSD2GenModel.
> at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
> at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months