[JBoss JIRA] (JBDS-4711) Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4711?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4711:
----------------------------------
Fix is in egit 5.0.1:
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=535917 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=535954.
> To fix, install EGit/JGit 5.0.1, or the nightly build.
> EGit 5.0.1: http://download.eclipse.org/egit/updates/
> EGit nightly: http://download.eclipse.org/egit/updates-nightly/
> Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4711
> URL: https://issues.jboss.org/browse/JBDS-4711
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 12.0.0.GA
> Environment: F28 + 12.0.0.GA-v20180625-0632-B2859
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 12.x
>
>
> After every start of devstudio, there is a warning:
> {code:java}
> eclipse.buildId=12.0.0.GA-v20180625-0632-B2859
> java.version=1.8.0_172
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2859_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.egit.core
> Warning
> Mon Jun 25 13:18:32 CEST 2018
> Builtin LFS support not present/detected
> java.lang.ClassNotFoundException: org.eclipse.jgit.lfs.BuiltinLFS cannot be found by org.eclipse.egit.core_5.0.0.201806131550-r
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:508)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.egit.core.Activator.registerBuiltinLFS(Activator.java:279)
> at org.eclipse.egit.core.Activator.start(Activator.java:212)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.egit.ui.Activator$RepositoryChangeScanner.<init>(Activator.java:921)
> at org.eclipse.egit.ui.Activator.setupRepoChangeScanner(Activator.java:1034)
> at org.eclipse.egit.ui.Activator.start(Activator.java:336)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60)
> at org.eclipse.ui.internal.services.WorkbenchServiceRegistry.getSourceProviders(WorkbenchServiceRegistry.java:174)
> at org.eclipse.ui.internal.services.SourceProviderService.readRegistry(SourceProviderService.java:104)
> at org.eclipse.ui.internal.Workbench$34.runWithException(Workbench.java:2378)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:32)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5831)
> at org.eclipse.ui.internal.StartupThreading.runWithoutExceptions(StartupThreading.java:95)
> at org.eclipse.ui.internal.Workbench.initializeDefaultServices(Workbench.java:2373)
> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1654)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2859)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1471)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26084) Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26084?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-26084:
------------------------------------------
the question here is how to find out that pod doesn't have services or replication controllers "above" it. What i think can work is to check "ownerReferences" field. I found out that it exists for pods that should be displayed under services and doesn't exist for pods that can be created using the description of https://issues.jboss.org/browse/JBIDE-25681.
[~adietish] wdyt?
[~jcantrill] [~deads2k] it would be great to have your opinion too, as i haven't found any mention of the "ownerReferences" field in the Openshift 2 documentation
> Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26084
> URL: https://issues.jboss.org/browse/JBIDE-26084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: explorer
> Fix For: 4.6.0.Final
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2018-06-06-10-33-55-241.png
>
>
> steps:
> # EXEC: Create a new application via the following custom template [^eap-without-service-nor-deploymentconfig.json]
> # EXEC: look into OpenShift explorer and see where the pods for the application are shown
> Result:
> They're listed twice, once as pods on their own and a 2nd time as children for the replication controller (that the template creates)
> !image-2018-06-06-10-33-55-241.png!
> Also see the discussion in the PR Also see discussion for the corresponding [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1748] for JBIDE-24979
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26093) Debugging Support
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26093?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-26093.
---------------------------------
Fix Version/s: 4.6.0.Final
Resolution: Done
Aside from the client implementing integration, server side is now complete.
> Debugging Support
> -----------------
>
> Key: JBIDE-26093
> URL: https://issues.jboss.org/browse/JBIDE-26093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.Final
>
>
> SSP clients needs to be able to either have the SSP launch a given server in debug mode, or, ask the SSP for a launch command with debug flags applied.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
by Matteo Barrese (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matteo Barrese updated JBIDE-26156:
-----------------------------------
Summary: "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables. (was: "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.)
> "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matteo Barrese
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
by Matteo Barrese (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matteo Barrese updated JBIDE-26156:
-----------------------------------
Steps to Reproduce:
Table A -> Table B with foreign key name name1
Table C -> Table B with foreign key name name1
Import the entities from db tables.
the hibernate tool, reading the scherma, do error in subject
was:
Table A -> Table B with foreign key name name1
Table C -> Table B with foreign key name name1
Import the entity from db tables.
the hibernate tool, reading the scherma, do error in subject
> "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matteo Barrese
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
by Matteo Barrese (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matteo Barrese updated JBIDE-26156:
-----------------------------------
Steps to Reproduce:
Table A -> Table B with foreign key name name1
Table C -> Table B with foreign key name name1
Import the entity from db tables.
the hibernate tool, reading the scherma, do error in subject
was:
Table A -> Table B with foreign key name name1
Table C -> Table B with foreign key name name1
import the entity from db table. reading the scherma the hibernate tool do error
> "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matteo Barrese
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
by Matteo Barrese (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matteo Barrese updated JBIDE-26156:
-----------------------------------
Description:
Default name of sql anywhere's foreign key is the name of the destination table.
If more tables link to same table, can be present di default more foreign key with same name.
importing the entities from db tables do the error in subject
Please manage this case.
was:
Default name of sql anywhere foreign key is the name of the destination table.
if more table link to idem table, can be present di default more foreign key with idem name.
Please manage this case.
> "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matteo Barrese
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
by Matteo Barrese (JIRA)
Matteo Barrese created JBIDE-26156:
--------------------------------------
Summary: "forein key name ([name]) mapped to different tables!" reading schema to import the entity from db tables.
Key: JBIDE-26156
URL: https://issues.jboss.org/browse/JBIDE-26156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.5.3.Final
Environment: Windows 8.1
Eclipse version: Oxygen.3a Release (4.7.3a)
Jboss Tools 4.5.3.Final
SAP Sql Anywhere v.17.0.8.4103
Reporter: Matteo Barrese
Priority: Critical
Default name of sql anywhere foreign key is the name of the destination table.
if more table link to idem table, can be present di default more foreign key with idem name.
Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months