В этом небольшом посте моего блога хотелось бы рассказать о решение возможной проблемы связанной с повседневным использованием великолепной и замечательной бесплатной среды разработки под названием Eclipse, которая чаще всего используется для написания кода на языке программирования Java, не смотря на то, что множественные редакции Эклипса поддерживают достаточно внушительное множество языков программирования.
Но давайте вернемся к делу. Проблема состоит в том, что при запуске программы в среде выполнения операционной системы Microsoft Windows может появится не приятное окно с сообщением об ошибке при запуске программы. При этом сообщение достаточно не многословно и ссылается на файл логов, который лежит в папке программы Eclipse. Сообщение следующего характера: an error occurred see the log file далее следует имя файла логов в котором достаточно большое количество строк, которые мало, что могут сказать не опытному пользователю программы об ошибке. Как ни странно в российском сегменте глобальной сети Интернет решения данной проблемы я не нашел.
Как правило суть данной проблемы заключается в том, что у вас не определена так называемая рабочая папка, проще говоря у вас не задана папка JDK или JRE. Это может возникнуть в случае если вы обновили какую-либо из вышеописанных библиотек или установили новую, в общем пути сбились и их надо заново прописать. Проверить так ли это можно следующим образом: вызываете командную строку Windows и пишите простую команду «java» (без кавычек), так же можно написать «javac», далее жмете на Enter для её выполнения. После этого на консоль должна выйти справочная информация об установленной в операционной системе виртуальной машине java. Если же вам выходит сообщение: «‘java’ не является внутренней или внешней командой, исполняемой программой или пакетным файлом», или же что-то подобное (в случае когда установлено несколько версий JDK или JRE может выводиться информация об ошибке версии), то в этом случае проблема, возникающая в IDE Eclipse, скорее всего связана именно с этим.
Значит необходимо вручную прописать пути до виртуальной машины Java. Для этого заходим в свойства «Моего компьютера» и на вкладке «Дополнительно» снизу окна жмем на кнопку «Переменные среды». В панели «Системные переменные пользователя <Имя пользователя>» ищем переменную «Path» и если её нет (её нет, если никто до этого не создавал, но обычно она есть), то жмем на кнопку «Создать» и в графе имени переменной пишем «Path» (без кавычек), а в ячейке значения прописываем путь до папки «bin» вашей редакции JDK или JRE. Обычно они находятся по адресу: «C:Program FilesJavajdk1.7.0_11bin», где jdk1.7.0_11 — папка с установленной jdk версии 1.7.0_11 (у вас может быть другой). В общем, проще пройти через «Проводник Windows» к этой папке и просто скопировать путь. После того как вставите путь жмете во всех окнах свойств «Моего компьютера» кнопку OK. После этого пробуйте заново задать команду java в cmd. В случае успеха вам будет показана справочная информация.
После проделанных действий проблема «an error occurred see the log file» при запуске Eclipse должна быть решена.
For me it was down to a locking/permissions bug on
(path to Eclipse IDE)configurationorg.eclipse.osgi.manager.fileTableLock
See here
Spring Tool Suite 4 (64 bit for Windows Server 2016)
Version: 4.2.2.RELEASE
Build Id: 201905232009
based on Eclipse
Version: 2.2.500.v20190307-0500
Build id: I20190307-0500
wouldn’t launch and a pop up dialog appeared saying:
launch error has occurred see log file null
(This became apparent from the latest text log file in the folder
(path to Eclipse IDE)configuration)
!ENTRY org.eclipse.osgi 4 0
2019-06-19 18:41:10.408
!MESSAGE Error reading configuration: C:optsts-4.2.2.RELEASEconfigurationorg.eclipse.osgi.manager.fileTableLock (Access is denied)
!STACK 0
java.io.FileNotFoundException: C:optsts-4.2.2.RELEASEconfigurationorg.eclipse.osgi.manager.fileTableLock (Access is denied)
...
I had to go and tweak the permissions via File Explorer (Full access).
It appeared as if the IDE was doing nothing for a while.
The splash screen for Spring Tool Suite (based on Eclipse) eventually disappeared and the IDE started up again.
Now everything is back working correctly again.
I. Troubleshooting the “An error has occurred. see the log file Eclipse .metadata.log” error.
Welcome to this tutorial on troubleshooting the “An error has occurred. see the log file Eclipse .metadata.log” error. If you are seeing this error message when starting the Eclipse Integrated Development Environment (IDE), you are not alone. Many users have encountered this issue, and it can be frustrating to try to figure out how to resolve it.
The “An error has occurred. see the log file Eclipse .metadata.log” error is usually caused by a problem with the Eclipse workspace or with one of the projects in the workspace. The error can occur for a variety of reasons, such as a corrupt workspace, a problem with the Eclipse installation, or a conflict with another program.
In this tutorial, we will walk you through a number of steps that you can try to fix the “An error has occurred. see the log file Eclipse .metadata.log” error and get Eclipse running smoothly again. We will start by explaining how to check the log file for more information about the error, and then move on to other troubleshooting steps like restarting Eclipse, checking for updates, and deleting the .metadata folder.
So if you are ready to get your Eclipse IDE up and running again, let’s get started!
II. Check the log file for more information
- Explain that the first step in troubleshooting this error is to check the .metadata.log file for more information about the error.
- Detail how to locate and open the .metadata.log file.
First step in troubleshooting this error.
The first step in troubleshooting the “An error has occurred. see the log file Eclipse .metadata.log” error is to check the log file for more information about the error. The log file, which is called .metadata.log, is located in the workspace directory and contains details about the cause of the error. By examining the log file, you may be able to get a better understanding of what is causing the error and how to fix it.
How to locate and open the .metadata.log file.
To locate and open the .metadata.log file, follow these steps:
- Close Eclipse if it is open.
- Navigate to the workspace directory. The default location for the workspace directory is C:Userscomputernameeclipse-workspace, but you may have set a different location when you first installed Eclipse.
- In the workspace directory, look for the .metadata.log file. It may be hidden, so you may need to show hidden files and folders to see it.
- Right-click on the .metadata.log file and select “Open with” > “Notepad” (or another text editor of your choice).
The .metadata.log file may be quite long and contain a lot of information, so it can be helpful to use the search function (Ctrl+F on Windows) to look for specific keywords or phrases. Some common error messages that you may see in the .metadata.log file include “Java was started but returned exit code=13”, “A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Eclipse”, and “An error occurred while automatically activating bundle org.eclipse.ui.workbench”.
If you are unable to find any useful information in the .metadata.log file, or if you are not comfortable reading log files, you can move on to the next troubleshooting step. However, if you do find a specific error message or problem in the log file, you may be able to use that information to resolve the issue.
III. Try restarting Eclipse
Sometimes, simply closing and reopening Eclipse can help resolve the “An error has occurred. see the log file Eclipse .metadata.log” error. This is because restarting Eclipse can help reset any temporary files or settings that may be causing the error. While this step may not work for all cases, it is worth trying as it is quick and easy to do.
Steps for closing and reopening Eclipse.
To close and reopen Eclipse, follow these steps:
- Click on the “X” in the top-right corner of the Eclipse window, or go to File > Exit.
- Reopen Eclipse by double-clicking on the Eclipse icon on your desktop or in your start menu.
If Eclipse starts up successfully after being closed and reopened, the error may have been caused by a temporary issue that has now been resolved. However, if the error persists, you will need to try the next troubleshooting step.
It’s also a good idea to make sure that Eclipse is up to date before trying to reopen it. To check for updates, go to Help > Check for Updates. If there are any updates available, follow the prompts to download and install them. Updating Eclipse may help resolve the error if it is caused by a bug or other issue that has been fixed in a more recent release.
IV. Check for updates to Eclipse
If you are getting the “An error has occurred. see the log file Eclipse .metadata.log” error, it’s a good idea to check for updates to Eclipse. Sometimes, a bug or other issue may have been fixed in a more recent release of Eclipse, and updating to the latest version may help resolve the error.
To check for updates to Eclipse, follow these steps:
- Start Eclipse if it is not already open.
- Go to Help > Check for Updates.
- If there are any updates available, a window will appear showing the updates that are available.
- Follow the prompts to download and install the updates.
It’s worth noting that updates to Eclipse may require a restart to complete the installation process. If you are prompted to restart after installing updates, click “Yes” to restart Eclipse.
If there are no updates available, or if updating Eclipse does not help resolve the “An error has occurred. see the log file Eclipse .metadata.log” error, you can move on to the next troubleshooting step.
It’s always a good idea to keep your software up to date, as updates often include bug fixes and performance improvements. So even if updating Eclipse does not help resolve the error in this case, it’s still a good practice to regularly check for updates to all of your software.
V. Delete the .metadata folder
If you are still getting the “An error has occurred. see the log file Eclipse .metadata.log” error after trying the previous troubleshooting steps, you may need to delete the .metadata folder. The .metadata folder, which is located in the workspace directory, contains metadata and other settings for your Eclipse workspace. If the folder becomes corrupt, it can cause errors like the one you are experiencing.
To delete the .metadata folder and restart Eclipse, follow these steps:
- Close Eclipse if it is open.
- Navigate to the workspace directory. The default location for the workspace directory is C:Userscomputernameeclipse-workspace, but you may have set a different location when you first installed Eclipse.
- In the workspace directory, look for the .metadata folder. It may be hidden, so you may need to show hidden files and folders to see it.
- Right-click on the .metadata folder and select “Delete”.
- Restart Eclipse by double-clicking on the Eclipse icon on your desktop or in your start menu.
When you start Eclipse after deleting the .metadata folder, the projects in your workspace will not be loaded by default. To load them back into Eclipse, do the following:
- Go to File > Import.
- In the Import window, select “Existing Projects into Workspace” and click Next.
- In the “Select root directory” field, browse to the directory where your projects are located.
- Select the projects you want to import and click Finish.
It’s worth noting that deleting the .metadata folder will reset your Eclipse workspace, so any custom settings or configurations you have made will be lost. However, if the .metadata folder was causing the “An error has occurred. see the log file Eclipse .metadata.log” error, deleting it should resolve the issue.
VI. Conclusion
In this tutorial, we have walked you through a number of steps that you can try to fix the “An error has occurred. see the log file Eclipse .metadata.log” error and get your Eclipse Integrated Development Environment (IDE) running smoothly again. We began by explaining how to check the log file for more information about the error, and then moved on to other troubleshooting steps like restarting Eclipse, checking for updates, and deleting the .metadata folder.
To recap, here are the steps you can try to fix the “An error has occurred. see the log file Eclipse .metadata.log” error:
- Check the log file for more information. The log file, which is called .metadata.log, is located in the workspace directory and contains details about the cause of the error.
- Try restarting Eclipse. Sometimes, simply closing and reopening Eclipse can help resolve the issue.
- Check for updates to Eclipse. Updating to the latest version of Eclipse may help resolve the error if it is caused by a bug or other issue that has been fixed in a more recent release.
- Delete the .metadata folder. If the .metadata folder becomes corrupt, it can cause errors like the one you are experiencing. Deleting the folder and restarting Eclipse can help resolve the error. However, keep in mind that deleting the .metadata folder will reset your Eclipse workspace, so any custom settings or configurations you have made will be lost.
If the above steps do not help resolve the “An error has occurred. see the log file Eclipse .metadata.log” error, it may be necessary to seek further assistance from the Eclipse support team or from a technical expert. The Eclipse support team is available to help users troubleshoot issues with the Eclipse IDE, and they may be able to provide more specific guidance on how to fix the error. Alternatively, you can seek assistance from a technical expert who is familiar with Eclipse and can help you troubleshoot the issue.
In conclusion, if you are getting the “An error has occurred. see the log file Eclipse .metadata.log” error when starting Eclipse, try checking the log file for more information, restarting Eclipse, checking for updates, and deleting the .metadata folder. If these steps do not help, you may need to seek further assistance from the Eclipse support team or from a technical expert. Remember to regularly back up your Eclipse projects to prevent data loss.
Video Tutorial.
Добрый день.
Уже облазил весь простор интернета, где я только не был что бы найти ответ на мой вопрос…
Но увы, ничего не помогло даже тот же Stack Overflow не дал результата.
Проблема заключается в следующем:
Установил я Eclipse oxygen 1, добавил в него TestNG и написал небольшой автотест.
Автотест не запустился вылезла ошибка, какая уже не помню, да и не вспомню…
Погулил, поискал, наткнулся на статью, где описывается решение данной проблемы переустановкой Java, вообщем всё так и сделал, переустановил последнюю версию JDK 9, прописал PATH/JAVA_HOME проверил в консоле всё ли правильно сделал 
всё вроде бы окей, запускаю и тут вот она, эта самая злостная ошибка, которая не даёт мне покоя уже второй день 
что я только не делал, и удалял файлы, чистил директории, переустанавливал Java, Eclipse тоже сносил снова ставил, разультат Нулевой.
может кто что подскажет, как вообще с этим быть?
spoiler
Эти все инструменты собирался использовать для автоматизации тестирования веб сайта.
не отрицаю что могут быть и лучше связки, чем Eclipse/TestNG/Selenium но я начал с этого, почему? даже не знаю, так вышло 
|
0 / 0 / 0 Регистрация: 14.10.2016 Сообщений: 40 |
|
|
1 |
|
|
29.10.2017, 13:27. Показов 14144. Ответов 6
Как исправить? Изображения
__________________
0 |
|
3636 / 2968 / 918 Регистрация: 05.07.2013 Сообщений: 14,220 |
|
|
29.10.2017, 14:33 |
2 |
|
написано же, смотри лог файл
0 |
|
0 / 0 / 0 Регистрация: 14.10.2016 Сообщений: 40 |
|
|
29.10.2017, 16:30 [ТС] |
3 |
|
От того, что я в него не посмотрел, проблема не решилась
0 |
|
2392 / 2218 / 564 Регистрация: 28.12.2010 Сообщений: 8,661 |
|
|
29.10.2017, 16:40 |
4 |
|
Ivan228, от того что ты лог тут не привел, проблема тоже не решилась.
0 |
|
0 / 0 / 0 Регистрация: 14.10.2016 Сообщений: 40 |
|
|
29.10.2017, 16:49 [ТС] |
5 |
|
0 |
|
2392 / 2218 / 564 Регистрация: 28.12.2010 Сообщений: 8,661 |
|
|
29.10.2017, 16:57 |
6 |
|
Решение
0 |
Сообщение было отмечено Ivan228 как решение
|
0 / 0 / 0 Регистрация: 14.10.2016 Сообщений: 40 |
|
|
29.10.2017, 18:52 [ТС] |
7 |
|
Спасибо, помогло.
0 |
June 1, 2017
To use eclipse we need to run exe of Eclipse, whenever I clicked on Eclipse icon
I got the same error pop-up every time , I tried installation of all Java’s JDK version ,
along with different Eclipse versions(Neon,Mars,Luna,Kepler,Helios) but none worked.
Friends, this error message has literally irritated me so much that I wanted
to avoid using Eclipse.I search all over the web to find the solution to this problem,
but I was nowhere.
I played with all the Java related Environment variables , added _JAVA_OPTIONS,
JAVA_HOME and JAVA_TOOL_OPTION and tried launching Eclipse , not worked.
I deleted all Env var and tried then too did not worked.I exhausted and frustrated .
Finally , I found the solution myself . God !!
Reason why all this happen because of cache date stored in cache Folder —
<<Your Eclipse Directory>>eclipsep2org.eclipse.equinox.p2.corecache
Cache folder contain startup setup files for workspace and other init files.
I deleted all the files in cache folder and guess what ? my problem solved !! .
I started Eclipse.exe and finally , I was on feeling relaxed .
Watch on Youtube-
Please feel free to share any other solution you came across through comments.
Author: Vikas Pandey
- GooglePlus
He is a software and web developer working for renowned European investment bank.He loves to share knowledge through blogging whatever he knows and encourages others as well to share the same to make world a better place to live.
Решено: eclipse 3.4 (An error has occurred. See the log file)
Модератор: /dev/random
-
Unit_1985
- Сообщения: 54
Решено: eclipse 3.4
собственно такая проблема: собрал eclipse 3.4 (USE = «doc java6»)
Но потом не могу его запустить пишет:
An error has occurred. See the log file
/home/unit/.eclipse/org.eclipse.platform_3.4.0_1169174241/configuration/1218004744826.log
В самом же этом файле находиться следующее
Код: Выделить всё
!SESSION 2008-08-06 10:39:04.633 -----------------------------------------------
eclipse.buildId=I20080617-2000
java.version=1.6.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=ru_RU
Framework arguments: -application
Command-line arguments: -os linux -ws gtk -arch x86 -consolelog -application
!ENTRY org.eclipse.update.configurator 4 0 2008-08-06 10:39:05.614
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() of bundle org.eclipse.update.configurator.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1028)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
Caused by: org.eclipse.core.runtime.CoreException: Cannot create configuration in file:/home/unit/.eclipse/org.eclipse.platform_3.4.0_1169174241/configuration/
at org.eclipse.update.internal.configurator.Utils.newCoreException(Utils.java:96)
at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:113)
at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
... 10 more
Root exception:
org.eclipse.core.runtime.CoreException: Cannot create configuration in file:/home/unit/.eclipse/org.eclipse.platform_3.4.0_1169174241/configuration/
at org.eclipse.update.internal.configurator.Utils.newCoreException(Utils.java:96)
at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:113)
at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
!ENTRY org.eclipse.core.runtime 4 0 2008-08-06 10:39:05.637
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.jobs; bundle-version="[3.2.0,4.0.0)"
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
!ENTRY org.eclipse.osgi 4 0 2008-08-06 10:39:05.641
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.update.configurator_3.2.200.v20080417.jar/ [2] is not active.
!ENTRY org.eclipse.osgi 4 0 2008-08-06 10:39:05.642
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.runtime_3.4.0.v20080512.jar/ was not resolved.
!ENTRY org.eclipse.osgi 4 0 2008-08-06 10:39:05.644
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
!ENTRY org.eclipse.osgi 2 0 2008-08-06 10:39:05.650
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-08-06 10:39:05.650
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.runtime_3.4.0.v20080512.jar/ was not resolved.
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.650
!MESSAGE Missing required bundle org.eclipse.equinox.registry_[3.4.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.651
!MESSAGE Missing required bundle org.eclipse.equinox.app_[1.0.0,2.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.651
!MESSAGE Missing required bundle org.eclipse.core.contenttype_[3.3.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.651
!MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.651
!MESSAGE Missing required bundle org.eclipse.equinox.preferences_[3.2.0,4.0.0).
!ENTRY org.eclipse.osgi 2 0 2008-08-06 10:39:05.652
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-08-06 10:39:05.653
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.runtime_3.4.0.v20080512.jar/ [3] was not resolved.
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.653
!MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.653
!MESSAGE Missing required bundle org.eclipse.equinox.registry_[3.4.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.653
!MESSAGE Missing required bundle org.eclipse.equinox.preferences_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.654
!MESSAGE Missing required bundle org.eclipse.core.contenttype_[3.3.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.654
!MESSAGE Missing optionally required bundle org.eclipse.core.runtime.compatibility.auth_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.654
!MESSAGE Missing required bundle org.eclipse.equinox.app_[1.0.0,2.0.0).
!SUBENTRY 2 org.eclipse.core.runtime 2 0 2008-08-06 10:39:05.654
!MESSAGE Missing imported package org.eclipse.core.internal.runtime.auth_0.0.0Что не так? Куда копать?
PS сборка с флагом -java6 ничего не изменила.
Вся жизнь игра и мы в ней юниты.
-
serzh-z
- Бывший модератор
- Сообщения: 8256
- Статус: Маньяк
- ОС: Arch, Fedora, Ubuntu
- Контактная информация:
Re: Решено: eclipse 3.4
Сообщение
serzh-z » 06.08.2008 12:26
А права на запись в тот самый каталог с конфигами есть? Может стоит удалить старую конфигурацию, пере запуском нового Eclipse?
-
Ali[SF]eN
- Сообщения: 33
- ОС: Gentoo / Slackware / FreeBSD
- Контактная информация:
Re: Решено: eclipse 3.4
Сообщение
Ali[SF]eN » 06.08.2008 14:30
возникла похожая трабла при сборке nexuiz-скачал tar и скомпилял вручную,тебе советую тоже самое
«Смерть одного человека-трагедия,смерть миллионов-статистика.»
И.В.Сталин
-
BuriK666
- Сообщения: 95
- ОС: GNU/Linux Gentoo
-
Контактная информация:
Re: Решено: eclipse 3.4
Сообщение
BuriK666 » 06.08.2008 17:01
Ali[SF]eN писал(а): ↑
06.08.2008 14:30
возникла похожая трабла при сборке nexuiz-скачал tar и скомпилял вручную,тебе советую тоже самое
это не Gentoo way, лучше написать ebuild.
Linux for you.
-
Atragor
- Сообщения: 681
- Статус: …
-
Контактная информация:
Re: Решено: eclipse 3.4
Сообщение
Atragor » 06.08.2008 18:11
А лучше проще скачать архив с бинарными файлами с оф. сайта, распаковать куда хочется и пользоваться.
If you were MEANT to understand it, we wouldn’t have called it ‘code’ © bash.org