directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-863) Installing from 2.x update site gives nothing to run on eclipse 3.8
Date Fri, 01 Feb 2013 09:41:14 GMT


Pierre-Arnaud Marcelot commented on DIRSTUDIO-863:


The log clearly indicates that Apache Directory Studio's views can't be opened.
> org.eclipse.ui.PartInitException: Could not create view:

Although, there's no specific exception explaining why...

There are 47 other exceptions (the same one each time) from another plugin:
> java.lang.NullPointerException
>	at com.adacore.gnatbench.spark.commands.SPARKMenuContributionItems.secureFill(

Given the list of features installed on your Eclipse installation, I think it might be a conflict
issue with other plugins.
Difficult to say at this stage.

Could you confirm Apache Directory Studio installation succeeds on a fresh and clean installation
of Eclipse 3.8 ?
> Installing from 2.x update site gives nothing to run on eclipse 3.8
> -------------------------------------------------------------------
>                 Key: DIRSTUDIO-863
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M3
>         Environment: Ubuntu 12.4.1 x64, eclipse 3.8, update site,
java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-0ubuntu1~12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>            Reporter: Vasiliy Molostov
>         Attachments: dirstudio-details.png, dirstudio-installed.png, dirstudio-missing-views.png,
dirstudio-preferences.png, .log, Screen Shot 2013-01-24 at 11.45.16.png, Screen Shot 2013-01-24
at 11.45.22.png
> Installation possible, but after eclipse 3.8 restart there is no views or perspectives
associated with 2.0 studio plugins: even preferences page is empty.
> Running standalone RCP works fine.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message