[JBoss JIRA] (JBIDE-22495) For JBIDE 4.4.0.Final: Prepare for Final/GA [Central]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22495?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-22495:
----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Central]
> -----------------------------------------------------
>
> Key: JBIDE-22495
> URL: https://issues.jboss.org/browse/JBIDE-22495
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Central]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22507:
-------------------------------------
Steps to Reproduce:
# EXEC: create a new application using eap64-basic-s2i and have it imported into your workspace
# EXEC: create a server adapter for the new service that was created: eap-app
# EXEC: restart the server adapter in debug mode
notice the following in your Eclipse log:
{code}
java.lang.NullPointerException
at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76)
at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167)
at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91)
at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
# EXEC: set a brk point in the source of your imported project
# EXEC: refresh browser so that your break-point is hit
Result:
Breakpoint never gets hit.
was:
# EXEC: create a new application using eap64-basic-s2i and have it imported into your workspace
# EXEC: create a server adapter for the new service that was created: eap-app
# EXEC: restart the server adapter in debug mode
notice the following in your Eclipse log:
{code}
java.lang.NullPointerException
at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76)
at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167)
at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91)
at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
#
> Debugging: cannot debug kitchensink, no breakpoint is being hit
> ---------------------------------------------------------------
>
> Key: JBIDE-22507
> URL: https://issues.jboss.org/browse/JBIDE-22507
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Fix For: 4.4.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22301:
-----------------------------------------------
[~mlabuda], it seems that we cannot to validate all details of specific template and user may rely on what server reports on failure. What is the error message in you case with template eap64. Was application at least partially created?
> NPE in new OS application from eclipse project with no remote git reference.
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha2
>
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22508:
----------------------------------
Summary: compile failed in org.jboss.tools.wtp.server.launchbar
Key: JBIDE-22508
URL: https://issues.jboss.org/browse/JBIDE-22508
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.0.Alpha2
Reporter: Nick Boldt
{code}
02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure:
02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325]
02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR);
02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^
02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field
{code}
-- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-241) IOOBE in DockerConnection.listImages [EBZ#495293]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-241:
---------------------------------------
Summary: IOOBE in DockerConnection.listImages [EBZ#495293]
Key: ERT-241
URL: https://issues.jboss.org/browse/ERT-241
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Using Docker Tools Neon RC3, I'm connecting to the Docker Connection from Red Hat's CDK. When expanding the connection in the Docker wizard, I get:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:940)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:867)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.setState(DockerConnection.java:307)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.ping(DockerConnection.java:322)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:265)
at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Looking at the images from the docker daemon in the CDK, I have:
[vagrant@rhel-cdk ~]$ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
172.30.212.99:5000/green-pond/nodejs-example latest cc67cf22130e 37 hours ago 462.7 MB
172.30.212.99:5000/green-pond/nodejs-example <none> cc67cf22130e 37 hours ago 462.7 MB
172.30.212.99:5000/red-lake/cakephp-example latest 6c27e86467b4 37 hours ago 508.7 MB
172.30.212.99:5000/red-lake/cakephp-example <none> 6c27e86467b4 37 hours ago 508.7 MB
172.30.212.99:5000/blue-ocean/nodejs-example latest a635e56be340 5 days ago 462.6 MB
172.30.212.99:5000/blue-ocean/nodejs-example <none> a635e56be340 5 days ago 462.6 MB
172.30.212.99:5000/sample-project/eap-app latest eb8d65658edc 6 days ago 1.216 GB
172.30.212.99:5000/sample-project/eap-app <none> eb8d65658edc 6 days ago 1.216 GB
172.30.212.99:5000/sample-project/eap-app <none> 643b71125b32 6 days ago 1.216 GB
172.30.212.99:5000/sample-project/nodejs-example latest a0dfe1b3736a 6 days ago 462.5 MB
172.30.212.99:5000/sample-project/nodejs-example <none> a0dfe1b3736a 6 days ago 462.5 MB
registry.access.redhat.com/openshift3/nodejs-010-rhel7 latest e0f62ad5808a 2 weeks ago 449.5 MB
docker.io/prom/haproxy-exporter latest f02e3d32d0e8 2 weeks ago 14.26 MB
registry.access.redhat.com/rhscl/php-56-rhel7 latest bbfc4eb8005b 3 weeks ago 491.4 MB
registry.access.redhat.com/openshift3/ose-haproxy-router v3.2.0.20 c1db351028fd 3 weeks ago 496.8 MB
registry.access.redhat.com/openshift3/ose-sti-builder v3.2.0.20 46dc17965ef6 3 weeks ago 481.6 MB
registry.access.redhat.com/openshift3/ose-deployer v3.2.0.20 009a6b612dc0 3 weeks ago 481.6 MB
registry.access.redhat.com/openshift3/ose-docker-registry v3.2.0.20 b51752f794c4 3 weeks ago 526.2 MB
registry.access.redhat.com/openshift3/ose v3.2.0.20 2aadff6087c7 3 weeks ago 481.6 MB
registry.access.redhat.com/openshift3/ose-pod v3.2.0.20 93bd54960c4b 3 weeks ago 215.2 MB
registry.access.redhat.com/jboss-eap-6/eap64-openshift 1.2 9a9678426f0c 5 weeks ago 1.209 GB
Also:
[vagrant@rhel-cdk ~]$ docker inspect --format='{{.RepoTags}}' cc67cf22130e
[172.30.212.99:5000/green-pond/nodejs-example:latest]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22508:
-------------------------------
Priority: Blocker (was: Major)
> compile failed in org.jboss.tools.wtp.server.launchbar
> --------------------------------------------------------
>
> Key: JBIDE-22508
> URL: https://issues.jboss.org/browse/JBIDE-22508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.0.Final
>
>
> {code}
> 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure:
> 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325]
> 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR);
> 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^
> 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22508:
-------------------------------
Fix Version/s: 4.4.0.Final
> compile failed in org.jboss.tools.wtp.server.launchbar
> --------------------------------------------------------
>
> Key: JBIDE-22508
> URL: https://issues.jboss.org/browse/JBIDE-22508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.0.Final
>
>
> {code}
> 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure:
> 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325]
> 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR);
> 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^
> 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months