[JBoss JIRA] (JBIDE-26173) Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26173?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26173:
---------------------------------------
Also, error appears in Error log:
java.io.IOException: Cannot run program "": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at org.jboss.tools.openshift.internal.core.preferences.OCBinaryValidator.getVersion(OCBinaryValidator.java:127)
at org.jboss.tools.openshift.internal.ui.preferences.OpenShiftPreferencePage$2.run(OpenShiftPreferencePage.java:178)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 3 more
I think that switching of validation for empty oc location could be better. What if user do not want to set oc in preferences but only in openshift connection (aka override oc location)?
> Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26173
> URL: https://issues.jboss.org/browse/JBIDE-26173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Priority: Critical
>
> When user chooses Preferences -> Jboss Tools -> OpenShift 3 and does nothing (ie. when one just clicked to wrong page), the page cannot be changed, 'Could not accept changes' dialog pops up and user must cancel Preferences dialog.
> I suggest to not validate empty oc location.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26173) Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-26173:
-------------------------------------
Summary: Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
Key: JBIDE-26173
URL: https://issues.jboss.org/browse/JBIDE-26173
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.Final
Reporter: Ondrej Dockal
Assignee: Andre Dietisheim
Priority: Critical
When user chooses Preferences -> Jboss Tools -> OpenShift 3 and does nothing (ie. when one just clicked to wrong page), the page cannot be changed, 'Could not accept changes' dialog pops up and user must cancel Preferences dialog.
I suggest to not validate empty oc location.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[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 updated JBDS-4711:
-----------------------------
Fix Version/s: 12.9.0.AM1
(was: 12.x)
> 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.9.0.AM1
>
>
> 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)
7 years, 9 months
[JBoss JIRA] (JBIDE-26172) Application wizard: cannot create apps via templates on OpenShift online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26172?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26172:
------------------------------------------
just tried the binary build in a vanilla Eclipse Photon and I can confirm that things work, JBDS works with OpenShift Online:
!openshift-online-nodejs-app-created.png!
> Application wizard: cannot create apps via templates on OpenShift online
> ------------------------------------------------------------------------
>
> Key: JBIDE-26172
> URL: https://issues.jboss.org/browse/JBIDE-26172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: OpenShift Online, OpenShift version 3.10.9
> !image-2018-07-05-16-30-38-168.png!
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-07-05-14-52-49-127.png, image-2018-07-05-16-30-38-168.png, openshift-online-nodejs-app-created.png
>
>
> steps:
> # ASSERT: have a connection to OpenShift Online (https://console.starter-us-west-1.openshift.com)
> # EXEC: launch application wizard via explorer ctx menu New > Application
> # EXEC: select a template (ex. nodejs-mongo-persistent), hit "Finish"
> Result:
> The wizard complains that the API version in the data for
> * route
> * image
> * build
> * apps
> does not match the expected API version v1.
> !image-2018-07-05-14-52-49-127.png!
> The services are create but other than that nothing is: neither bc, builds, rc, dc, is etc.
> There's no error in the Eclipse log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26172) Application wizard: cannot create apps via templates on OpenShift online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26172?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26172:
-------------------------------------
Attachment: openshift-online-nodejs-app-created.png
> Application wizard: cannot create apps via templates on OpenShift online
> ------------------------------------------------------------------------
>
> Key: JBIDE-26172
> URL: https://issues.jboss.org/browse/JBIDE-26172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: OpenShift Online, OpenShift version 3.10.9
> !image-2018-07-05-16-30-38-168.png!
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-07-05-14-52-49-127.png, image-2018-07-05-16-30-38-168.png, openshift-online-nodejs-app-created.png
>
>
> steps:
> # ASSERT: have a connection to OpenShift Online (https://console.starter-us-west-1.openshift.com)
> # EXEC: launch application wizard via explorer ctx menu New > Application
> # EXEC: select a template (ex. nodejs-mongo-persistent), hit "Finish"
> Result:
> The wizard complains that the API version in the data for
> * route
> * image
> * build
> * apps
> does not match the expected API version v1.
> !image-2018-07-05-14-52-49-127.png!
> The services are create but other than that nothing is: neither bc, builds, rc, dc, is etc.
> There's no error in the Eclipse log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26156) Error "foreign key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
by Matt B (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matt B updated JBIDE-26156:
---------------------------
Summary: Error "foreign 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 entities from db tables.)
> Error "foreign 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
> Hibernate 5.2.17
> Reporter: Matt B
> Assignee: Koen Aers
> 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)
7 years, 9 months
[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26157:
-------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.9.x)
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, server
> Reporter: Dawid Olejnik
> Assignee: Jeff MAURY
> Fix For: 4.6.0.Final
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
> Steps to reproduce:
> * create a dynamic web project and set servlet facet version to 4.0
> * create a Wildfly 13 or 12 instance
> * try to add the project to the server and you will get the dialog
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26172) Application wizard: cannot create apps via templates on OpenShift online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26172?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26172:
-------------------------------------
Sprint: devex #151 June 2018
> Application wizard: cannot create apps via templates on OpenShift online
> ------------------------------------------------------------------------
>
> Key: JBIDE-26172
> URL: https://issues.jboss.org/browse/JBIDE-26172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: OpenShift Online, OpenShift version 3.10.9
> !image-2018-07-05-16-30-38-168.png!
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-07-05-14-52-49-127.png, image-2018-07-05-16-30-38-168.png
>
>
> steps:
> # ASSERT: have a connection to OpenShift Online (https://console.starter-us-west-1.openshift.com)
> # EXEC: launch application wizard via explorer ctx menu New > Application
> # EXEC: select a template (ex. nodejs-mongo-persistent), hit "Finish"
> Result:
> The wizard complains that the API version in the data for
> * route
> * image
> * build
> * apps
> does not match the expected API version v1.
> !image-2018-07-05-14-52-49-127.png!
> The services are create but other than that nothing is: neither bc, builds, rc, dc, is etc.
> There's no error in the Eclipse log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months