[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3598 at 2/18/16 10:14 AM:
------------------------------------------------------------
Turns out this is caused by trying to build a maven project w/o the .git metadata folder being present.
So I need to add the .git folder into the repo so that one can build from the sources zip.
Or we could migrate the sources to a public github repo and stop providing a zip entirely.
[~maxandersen] [~akazakov] WDYT? Is it time to move https://github.com/jbdevstudio/jbdevstudio-product to https://github.com/jbosstools/jbdevstudio-product ?
was (Author: nickboldt):
Smells like an OS bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1196167
Or, it's a corruption in Maven metadata repo problem:
http://stackoverflow.com/questions/19143534/hudson-error-when-checking-ou...
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21714) ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21714?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-21714:
-----------------------------------------
you're welcome :-)
sorry for the wrong JIRA project issue report
> ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21714
> URL: https://issues.jboss.org/browse/JBIDE-21714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Aurélien Pupier
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: dndSTack.png
>
>
> 1. DnD an external file onto JBDS Editor site
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2016-02-18 10:50:09.183
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124)
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.drop(JBossCentralDropTarget.java:90)
> at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:91)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:788)
> at org.eclipse.swt.dnd.DropTarget.Drop(DropTarget.java:456)
> at org.eclipse.swt.dnd.DropTarget.Drop_64(DropTarget.java:392)
> at org.eclipse.swt.dnd.DropTarget$3.method6(DropTarget.java:260)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21714) ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21714?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21714:
-----------------------------------
Fix Version/s: 4.3.1.CR1
Assignee: Fred Bricon
Resolution: Done
PR applied in master and 4.3.x. Thanks Aurélien!
> ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21714
> URL: https://issues.jboss.org/browse/JBIDE-21714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Aurélien Pupier
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: dndSTack.png
>
>
> 1. DnD an external file onto JBDS Editor site
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2016-02-18 10:50:09.183
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124)
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.drop(JBossCentralDropTarget.java:90)
> at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:91)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:788)
> at org.eclipse.swt.dnd.DropTarget.Drop(DropTarget.java:456)
> at org.eclipse.swt.dnd.DropTarget.Drop_64(DropTarget.java:392)
> at org.eclipse.swt.dnd.DropTarget$3.method6(DropTarget.java:260)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21714) ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21714?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21714:
--------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-21714 (was: JBDS-3597)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: central
(was: central)
Affects Version/s: 4.3.0.Final
(was: 9.1.0.Beta1)
> ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21714
> URL: https://issues.jboss.org/browse/JBIDE-21714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Aurélien Pupier
> Priority: Minor
> Attachments: dndSTack.png
>
>
> 1. DnD an external file onto JBDS Editor site
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2016-02-18 10:50:09.183
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124)
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.drop(JBossCentralDropTarget.java:90)
> at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:91)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:788)
> at org.eclipse.swt.dnd.DropTarget.Drop(DropTarget.java:456)
> at org.eclipse.swt.dnd.DropTarget.Drop_64(DropTarget.java:392)
> at org.eclipse.swt.dnd.DropTarget$3.method6(DropTarget.java:260)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3598:
----------------------------------
Smells like an OS bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1196167
Or, it's a corruption in Maven metadata repo problem:
http://stackoverflow.com/questions/19143534/hudson-error-when-checking-ou...
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21710) [CDK] replace calls to adbinfo plugin with service-manager plugin
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21710?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21710:
--------------------------------
Summary: [CDK] replace calls to adbinfo plugin with service-manager plugin (was: replace calls to adbinfo plugin with service-manager plugin)
> [CDK] replace calls to adbinfo plugin with service-manager plugin
> -----------------------------------------------------------------
>
> Key: JBIDE-21710
> URL: https://issues.jboss.org/browse/JBIDE-21710
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, openshift, server
> Reporter: Navid Shaikh
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> vagrant-service-manager plugin [1] is a successor for vagrant-adbinfo plugin [2].
> All further development towards displaying and configuring provider [docker, openshift, kubernetes, etc] information from ADB / CDK, will happen in vagrant-service-manager plugin.
> Equivalent functionality from vagrant-adbinfo plugin is now ported to vagrant-service-manager plugin.
> To display docker connection information from vagrant box,
> using adbinfo
> ```
> $ vagrant adbinfo
> ```
> using service-manager
> ```
> $vagrant service-manager env docker
> ```
> Kindly update the tooling which are using adbinfo plugin with service-manager command.
> Note: adbinfo plugin has a dependency on `scp` / `pscp` utility for copying certs. service-manager plugin does not need `scp` / `pscp` utility to copy the certs.
> [1] https://github.com/projectatomic/vagrant-service-manager
> [2] https://github.com/projectatomic/vagrant-adbinfo
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21686) Eclipse freeze when trying to reconnect to an existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21686:
------------------------------------------
merged into jbosstools-4.3.x
> Eclipse freeze when trying to reconnect to an existing connection
> -----------------------------------------------------------------
>
> Key: JBIDE-21686
> URL: https://issues.jboss.org/browse/JBIDE-21686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment:
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> On nightly build of OpenShift tooling when I am trying to reconnect to an existing connection, whole IDE freeze. E.g. after restart of eclipse and token to server has not been stored in secure storage, I am prompted to enter token when trying to do anything with an existing OS3 connection and upon entering a token and hitting Finish button, IDE freeze and after a while its not responding.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21713) Eclipse freeze when trying to reconnect to an existing connection
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21713:
----------------------------------------
Summary: Eclipse freeze when trying to reconnect to an existing connection
Key: JBIDE-21713
URL: https://issues.jboss.org/browse/JBIDE-21713
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Environment:
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.3.1.CR1
On nightly build of OpenShift tooling when I am trying to reconnect to an existing connection, whole IDE freeze. E.g. after restart of eclipse and token to server has not been stored in secure storage, I am prompted to enter token when trying to do anything with an existing OS3 connection and upon entering a token and hitting Finish button, IDE freeze and after a while its not responding.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21713) Eclipse freeze when trying to reconnect to an existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21713?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21713:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Eclipse freeze when trying to reconnect to an existing connection
> -----------------------------------------------------------------
>
> Key: JBIDE-21713
> URL: https://issues.jboss.org/browse/JBIDE-21713
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment:
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> On nightly build of OpenShift tooling when I am trying to reconnect to an existing connection, whole IDE freeze. E.g. after restart of eclipse and token to server has not been stored in secure storage, I am prompted to enter token when trying to do anything with an existing OS3 connection and upon entering a token and hitting Finish button, IDE freeze and after a while its not responding.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month