Studio release - dependencies
Hi all, I consider doing a Studio release, upgrading to Eclipse Oxygen to fix issues with Java 9. But there are quite some dependencies. * I think last time I tried sSome Studio UI tests failed which needs to be fixed first. * Server master currently doesn't build because of compilation failure. * Studio currently depends on API 2.0.0.AM1-SNAPSHOT and Server 2.0.0.AM25-SNAPSHOT which would need to be released first. And I have no idea if those are release "ready". * I'm not sure if the Server version 2.0.0.AM25 will work for the update sie because that version is smaller than 2.0.0.M24 what the previous release used. Kind Regards, Stefan
[jira] [Closed] (DIRSTUDIO-1168) Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann closed DIRSTUDIO-1168. -- Resolution: Won't Fix > Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS > -- > > Key: DIRSTUDIO-1168 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1168 > Project: Directory Studio > Issue Type: Bug > Components: studio-installer >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > > After installing the MacOS DMG packaged version of ADS, the name of the > package had changed to "ApacheDirectoryStudio" instead of "Apache Directory > Studio". > This broke the upgrade, as the overwrite of the previous version of ADS > failed. > To fix this, the name needs to be reinstated to "Apache Directory Studio". > This also affects the packagename in the top right corner of the menu when > the application runs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1168) Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369561#comment-16369561 ] Stefan Seelmann commented on DIRSTUDIO-1168: The name was changed back in 2015 in Studio 2.0.0-M9 because we changed the build system and the application name was inconsistend for Windows, Linux, and Mac. I don't think we change it back because that would break upgrades too. > Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS > -- > > Key: DIRSTUDIO-1168 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1168 > Project: Directory Studio > Issue Type: Bug > Components: studio-installer >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > > After installing the MacOS DMG packaged version of ADS, the name of the > package had changed to "ApacheDirectoryStudio" instead of "Apache Directory > Studio". > This broke the upgrade, as the overwrite of the previous version of ADS > failed. > To fix this, the name needs to be reinstated to "Apache Directory Studio". > This also affects the packagename in the top right corner of the menu when > the application runs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1169) Usability: "An error has occurred" on startup
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369553#comment-16369553 ] Stefan Seelmann commented on DIRSTUDIO-1169: I'm afraid that we cannot do much about that because the dialog is presented by the underlying Eclipse framework. On Linux I'm able to copy the text from the dialog so I assume it's Mac specific. Maybe one wants to file a bug/enhancement at Eclipse? :) > Usability: "An error has occurred" on startup > - > > Key: DIRSTUDIO-1169 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1169 > Project: Directory Studio > Issue Type: Bug > Components: studio-rcp >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > Attachments: ads-an-error-has-occurred.png > > > After upgrading Java to v9.0.4 and Apache Directory Studio to v2.2.0-M13, an > attempt to run the application for the first time stops with a popup saying: > "An error has occurred > See the log file > XXX" > At the same time the error message is selectable, but cannot be > cut-and-pasted, leaving you to transcribe the log file path by hand. > Ideally the error should appear in the popup itself directly, and the error > message must be copy-able so as to put it into google. > Note: this ticket covers the usability of the error message, not the error > itself. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1158) Studio doesn't start with Java 9 (GA)
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369550#comment-16369550
]
Konrad Windszus commented on DIRSTUDIO-1158:
Both issues are now closed as DUPLICATE of each other. Please keep at least one
open to allow to track the progress until Studio is upgraded to Oxygen.
> Studio doesn't start with Java 9 (GA)
> -
>
> Key: DIRSTUDIO-1158
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1158
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-apacheds
>Affects Versions: 2.0.0-M13
> Environment: Java 9
>Reporter: Jesse Sandstrom
>Assignee: Stefan Seelmann
>Priority: Major
>
> Studio M13 doesn't start with final release of Java 9.
> Workaround is to add to append to the ApacheDirectoryStudio.ini file the
> following line {{--add-modules=ALL-SYSTEM}}.
> This seems to be a generic problem with Eclipse Neon and Oxygen. (Reference
> https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_for_Java_9_modules)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1162) Application does not launch with Oracle JDK9
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369545#comment-16369545
]
Stefan Seelmann commented on DIRSTUDIO-1162:
See linked issue, workaround until Studio is upgraded to Eclispe Oxygen
platform is to add "--add-modules=ALL-SYSTEM" to the end of the
ApacheDirectoryStudio.ini file. This is only required for Oracle Java 9 (tested
with 9.0.4), OpenJDK 9 enables that flag by default.
> Application does not launch with Oracle JDK9
>
>
> Key: DIRSTUDIO-1162
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1162
> Project: Directory Studio
> Issue Type: Bug
>Affects Versions: 2.0.0-M13
> Environment: ArchLinux, kernel 4.13.11-1-ARCH
> Oracle Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
>Reporter: Mohammed Lee
>Priority: Major
> Labels: usability
> Attachments: .log
>
>
> Starting the application with this simple wrapper script:
> #! /bin/sh
> export PATH="/opt/java9/bin:${PATH}"
> exec /opt/ApacheDirectoryStudio/ApacheDirectoryStudio "${@}"
> If PATH points to the most recent Oracle JDK 8, application works fine, but
> if it points to the most recent Oracle JDK 9, application crashes right after
> splash screen is displayed; logging file is attached to this ticket.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DIRSTUDIO-1162) Application does not launch with Oracle JDK9
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann closed DIRSTUDIO-1162.
--
Resolution: Duplicate
> Application does not launch with Oracle JDK9
>
>
> Key: DIRSTUDIO-1162
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1162
> Project: Directory Studio
> Issue Type: Bug
>Affects Versions: 2.0.0-M13
> Environment: ArchLinux, kernel 4.13.11-1-ARCH
> Oracle Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
>Reporter: Mohammed Lee
>Priority: Major
> Labels: usability
> Attachments: .log
>
>
> Starting the application with this simple wrapper script:
> #! /bin/sh
> export PATH="/opt/java9/bin:${PATH}"
> exec /opt/ApacheDirectoryStudio/ApacheDirectoryStudio "${@}"
> If PATH points to the most recent Oracle JDK 8, application works fine, but
> if it points to the most recent Oracle JDK 9, application crashes right after
> splash screen is displayed; logging file is attached to this ticket.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DIRSTUDIO-1158) Studio doesn't start with Java 9 (GA)
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann closed DIRSTUDIO-1158.
--
Resolution: Duplicate
> Studio doesn't start with Java 9 (GA)
> -
>
> Key: DIRSTUDIO-1158
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1158
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-apacheds
>Affects Versions: 2.0.0-M13
> Environment: Java 9
>Reporter: Jesse Sandstrom
>Assignee: Stefan Seelmann
>Priority: Major
>
> Studio M13 doesn't start with final release of Java 9.
> Workaround is to add to append to the ApacheDirectoryStudio.ini file the
> following line {{--add-modules=ALL-SYSTEM}}.
> This seems to be a generic problem with Eclipse Neon and Oxygen. (Reference
> https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_for_Java_9_modules)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1158) Studio doesn't start with Java 9 (GA)
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369543#comment-16369543
]
Stefan Seelmann commented on DIRSTUDIO-1158:
See linked issue, workaround until Studio is upgraded to Eclispe Oxygen
platform is to add "--add-modules=ALL-SYSTEM" to the end of the
ApacheDirectoryStudio.ini file. This is only required for Oracle Java 9 (tested
with 9.0.4), OpenJDK 9 enables that flag by default.
> Studio doesn't start with Java 9 (GA)
> -
>
> Key: DIRSTUDIO-1158
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1158
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-apacheds
>Affects Versions: 2.0.0-M13
> Environment: Java 9
>Reporter: Jesse Sandstrom
>Assignee: Stefan Seelmann
>Priority: Major
>
> Studio M13 doesn't start with final release of Java 9.
> Workaround is to add to append to the ApacheDirectoryStudio.ini file the
> following line {{--add-modules=ALL-SYSTEM}}.
> This seems to be a generic problem with Eclipse Neon and Oxygen. (Reference
> https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_for_Java_9_modules)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1170) Java9 startup failed: org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369541#comment-16369541 ] Stefan Seelmann commented on DIRSTUDIO-1170: See linked issue, workaround until Studio is upgraded to Eclispe Oxygen platform is to add "--add-modules=ALL-SYSTEM" to the end of the ApacheDirectoryStudio.ini file. This is only required for Oracle Java 9 (tested with 9.0.4), OpenJDK 9 enables that flag by default. > Java9 startup failed: org.eclipse.e4.core.di.InjectionException: > java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > --- > > Key: DIRSTUDIO-1170 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1170 > Project: Directory Studio > Issue Type: Bug > Components: studio-rcp >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > > After upgrading Java to v9.0.4 on MacOS Sierra, and upgrading ADS to > v2.0.0-M13, ADS crashes on startup as follows: > > !ENTRY org.eclipse.core.jobs 2 2 2018-02-19 19:20:44.586 > !MESSAGE Job found still running after platform shutdown. Jobs should be > canceled by the plugin that scheduled them during shutdown: > org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 > !SESSION 2018-02-19 19:41:57.838 > --- > eclipse.buildId=unknown > java.version=9.0.4 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_ZA > Framework arguments: /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 > /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > > !ENTRY org.eclipse.osgi 4 0 2018-02-19 19:42:03.403 > !MESSAGE Application error > !STACK 1 > org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: > javax/annotation/PostConstruct > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at > org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:632) > at > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.apache.directory.studio.Application.start(Application.java:51) > 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > 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) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct > cannot be found by org.eclipse.e4.core.di_1.6.1.v20160712-0927 > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:410) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at > org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at
[jira] [Closed] (DIRSTUDIO-1170) Java9 startup failed: org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann closed DIRSTUDIO-1170. -- Resolution: Duplicate > Java9 startup failed: org.eclipse.e4.core.di.InjectionException: > java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > --- > > Key: DIRSTUDIO-1170 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1170 > Project: Directory Studio > Issue Type: Bug > Components: studio-rcp >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > > After upgrading Java to v9.0.4 on MacOS Sierra, and upgrading ADS to > v2.0.0-M13, ADS crashes on startup as follows: > > !ENTRY org.eclipse.core.jobs 2 2 2018-02-19 19:20:44.586 > !MESSAGE Job found still running after platform shutdown. Jobs should be > canceled by the plugin that scheduled them during shutdown: > org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 > !SESSION 2018-02-19 19:41:57.838 > --- > eclipse.buildId=unknown > java.version=9.0.4 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_ZA > Framework arguments: /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 > /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > > !ENTRY org.eclipse.osgi 4 0 2018-02-19 19:42:03.403 > !MESSAGE Application error > !STACK 1 > org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: > javax/annotation/PostConstruct > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at > org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:632) > at > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.apache.directory.studio.Application.start(Application.java:51) > 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > 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) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct > cannot be found by org.eclipse.e4.core.di_1.6.1.v20160712-0927 > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:410) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at > org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496) > ... 24 more > > !ENTRY org.eclipse.e4.ui.workbench 4 0 2018-02-19 19:42:03.413 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > java.lang.NoClassDefFoundError: javax/annotation/PreDestroy > at >
Re: Studio and Java9
Le 19/02/2018 à 19:25, Graham Leggett a écrit : > Hi all, > > I just upgraded to Java9 so I could work on elasticsearch, and in the process > it broke Studio v2.0.0-M13. > > According to https://java.com/en/uninstall/attachmentA.xml Oracle now > replaces the previous JDK when upgrading to the next JDK, so running on older > version is no longer possible. > > What prevents ADS working? Clearly, Java 9. And we are certainly not going to support it, as it will be EOL in March. Same thing for Java 10 / 18.3, which will EOL in september. Atm, just uninstall Java 9, keep going with Java 8 which is supported up to 2020. Don't buy the stupid Oracle agenda. It's crap. Utter crap. Shame on them. -- Emmanuel Lecharny Symas.com directory.apache.org
Studio and Java9
Hi all, I just upgraded to Java9 so I could work on elasticsearch, and in the process it broke Studio v2.0.0-M13. According to https://java.com/en/uninstall/attachmentA.xml Oracle now replaces the previous JDK when upgrading to the next JDK, so running on older version is no longer possible. What prevents ADS working? Regards, Graham — smime.p7s Description: S/MIME cryptographic signature
[jira] [Commented] (DIRSTUDIO-1170) Java9 startup failed: org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369388#comment-16369388 ] Graham Leggett commented on DIRSTUDIO-1170: --- Appears that due to this lawsuit that Oracle lost, multiple JDKs cannot be installed on the same machine at the same time: [https://java.com/en/uninstall/attachmentA.xml] > Java9 startup failed: org.eclipse.e4.core.di.InjectionException: > java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > --- > > Key: DIRSTUDIO-1170 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1170 > Project: Directory Studio > Issue Type: Bug > Components: studio-rcp >Affects Versions: 2.0.0-M13 >Reporter: Graham Leggett >Priority: Major > > After upgrading Java to v9.0.4 on MacOS Sierra, and upgrading ADS to > v2.0.0-M13, ADS crashes on startup as follows: > > !ENTRY org.eclipse.core.jobs 2 2 2018-02-19 19:20:44.586 > !MESSAGE Job found still running after platform shutdown. Jobs should be > canceled by the plugin that scheduled them during shutdown: > org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 > !SESSION 2018-02-19 19:41:57.838 > --- > eclipse.buildId=unknown > java.version=9.0.4 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_ZA > Framework arguments: /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 > /studio-rcp/resources/icons/linux/studio.xpm -keyring > /Users/minfrin/.eclipse_keyring > > !ENTRY org.eclipse.osgi 4 0 2018-02-19 19:42:03.403 > !MESSAGE Application error > !STACK 1 > org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: > javax/annotation/PostConstruct > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at > org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) > at > org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:632) > at > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.apache.directory.studio.Application.start(Application.java:51) > 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > 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) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at > org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct > cannot be found by org.eclipse.e4.core.di_1.6.1.v20160712-0927 > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:410) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at > org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496) > ... 24 more > > !ENTRY
[jira] [Created] (DIRSTUDIO-1170) Java9 startup failed: org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
Graham Leggett created DIRSTUDIO-1170: - Summary: Java9 startup failed: org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct Key: DIRSTUDIO-1170 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1170 Project: Directory Studio Issue Type: Bug Components: studio-rcp Affects Versions: 2.0.0-M13 Reporter: Graham Leggett After upgrading Java to v9.0.4 on MacOS Sierra, and upgrading ADS to v2.0.0-M13, ADS crashes on startup as follows: !ENTRY org.eclipse.core.jobs 2 2 2018-02-19 19:20:44.586 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 !SESSION 2018-02-19 19:41:57.838 --- eclipse.buildId=unknown java.version=9.0.4 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_ZA Framework arguments: /studio-rcp/resources/icons/linux/studio.xpm -keyring /Users/minfrin/.eclipse_keyring Command-line arguments: -os macosx -ws cocoa -arch x86_64 /studio-rcp/resources/icons/linux/studio.xpm -keyring /Users/minfrin/.eclipse_keyring !ENTRY org.eclipse.osgi 4 0 2018-02-19 19:42:03.403 !MESSAGE Application error !STACK 1 org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:632) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.apache.directory.studio.Application.start(Application.java:51) 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) 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) Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) ... 22 more Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.1.v20160712-0927 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:410) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496) ... 24 more !ENTRY org.eclipse.e4.ui.workbench 4 0 2018-02-19 19:42:03.413 !MESSAGE FrameworkEvent ERROR !STACK 0 java.lang.NoClassDefFoundError: javax/annotation/PreDestroy at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426) at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154) at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) at
[jira] [Created] (DIRSTUDIO-1169) Usability: "An error has occurred" on startup
Graham Leggett created DIRSTUDIO-1169: - Summary: Usability: "An error has occurred" on startup Key: DIRSTUDIO-1169 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1169 Project: Directory Studio Issue Type: Bug Components: studio-rcp Affects Versions: 2.0.0-M13 Reporter: Graham Leggett Attachments: ads-an-error-has-occurred.png After upgrading Java to v9.0.4 and Apache Directory Studio to v2.2.0-M13, an attempt to run the application for the first time stops with a popup saying: "An error has occurred See the log file XXX" At the same time the error message is selectable, but cannot be cut-and-pasted, leaving you to transcribe the log file path by hand. Ideally the error should appear in the popup itself directly, and the error message must be copy-able so as to put it into google. Note: this ticket covers the usability of the error message, not the error itself. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DIRSTUDIO-1168) Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS
Graham Leggett created DIRSTUDIO-1168: - Summary: Apache Directory Studio name changed to ApacheDirectoryStudio on MacOS Key: DIRSTUDIO-1168 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1168 Project: Directory Studio Issue Type: Bug Components: studio-installer Affects Versions: 2.0.0-M13 Reporter: Graham Leggett After installing the MacOS DMG packaged version of ADS, the name of the package had changed to "ApacheDirectoryStudio" instead of "Apache Directory Studio". This broke the upgrade, as the overwrite of the previous version of ADS failed. To fix this, the name needs to be reinstated to "Apache Directory Studio". This also affects the packagename in the top right corner of the menu when the application runs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
