I have troubles trying to import an already existing Symfony 2.3 project into my Eclipse (standard 4.3.1) workspace using dubture's plugin.
I use the Eclipse wizard for importing, but when I click on 'Finish' a popup window shows:
An error ocurred during import. Please see the workspace logs for details.
The log file gives me a bunch of messages like this one:
!ENTRY org.eclipse.dltk.core 2 0 2014-02-18 18:08:35.104
!MESSAGE Error receiving file: /Symfony/app/cache/dev/twig/d1/4c/d23835735a18dbf9b98dd75484f6.php content: retrying(1)
!STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource /Symfony/app/cache/dev/twig/d1/4c/d23835735a18dbf9b98dd75484f6.php' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
at org.eclipse.core.internal.resources.File.getContents(File.java:287)
at org.eclipse.dltk.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:534)
at org.eclipse.dltk.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:491)
at org.eclipse.dltk.internal.core.SourceModule.getBufferContent(SourceModule.java:405)
at org.eclipse.dltk.internal.core.AbstractSourceModule.getSourceAsCharArray(AbstractSourceModule.java:314)
at org.eclipse.dltk.internal.core.AbstractSourceModule.getContentsAsCharArray(AbstractSourceModule.java:335)
at org.eclipse.php.internal.core.compiler.ast.parser.AbstractPHPSourceParser.parse(AbstractPHPSourceParser.java:41)
at org.eclipse.php.internal.core.compiler.ast.parser.PHPSourceParserFactory.parse(PHPSourceParserFactory.java:41)
at com.dubture.twig.core.parser.TwigSourceParserFactory.parse(TwigSourceParserFactory.java:36)
at org.eclipse.dltk.core.SourceParserUtil.parse(SourceParserUtil.java:135)
at org.eclipse.dltk.core.SourceParserUtil.getModuleDeclaration(SourceParserUtil.java:171)
at org.eclipse.dltk.core.SourceParserUtil.getModuleDeclaration(SourceParserUtil.java:166)
at org.eclipse.php.internal.core.index.PhpIndexingParser.parseSourceModule(PhpIndexingParser.java:27)
at org.eclipse.dltk.core.index2.AbstractIndexer.indexDocument(AbstractIndexer.java:45)
at org.eclipse.dltk.internal.core.index.sql.SqlIndexer.indexDocument(SqlIndexer.java:147)
at org.eclipse.dltk.internal.core.index2.SourceModulesRequest.run(SourceModulesRequest.java:78)
at org.eclipse.dltk.core.search.indexing.AbstractJob.execute(AbstractJob.java:76)
at org.eclipse.dltk.internal.core.search.processing.JobManager.run(JobManager.java:467)
at java.lang.Thread.run(Unknown Source)
!SUBENTRY 1 org.eclipse.core.resources 4 368 2014-02-18 18:08:35.104
!MESSAGE Resource '/Symfony/app/cache/dev/twig/d1/4c/d23835735a18dbf9b98dd75484f6.php' does not exist.
I checked if the specified files exist and they do, so I don't understand these messages. Anyone had the same problem and can point me in the right direction?
You have to make sure youre vendors are installed correctly and also make sure you have a php executable running.
In eclipse menu :
window -> preferences -> Php -> php executables.
If you have nothing there :
Click add -> browse the executable (normaly /usr/bin/php5).
use zend debugger and check the "use defaults php.ini" box.
Related
I'm trying to use OProfile on Eclipse (3.8). The Juno version of oprofile didn't work, so I installed the Luna one. This one at least starts up, but can never find the libraries.
Here is the error:
ns3-dev-lena-profiling-debug: error while loading shared libraries: libns3-dev-lte- debug.so: cannot open shared object file: No such file or directory
profiled app exited with the following status: 127
I know that that means I need to add the library path. So I went to Profiling Tools Configurations, and specified the path under environmental variables as:
name: LD_LIBRARY_PATH
value: {workspace_loc:ns3dev2}/build (appended)
I manually checked and the library is located in the build folder. Furthermore, this library path works fine if I debug the same project instead (or run it...).
I've deleted the configuration and remade it, but it's the same error.
I also tried adding the same path to PATH instead of LD_LIBRARY_PATH, but that doesn't make any difference. (Just tried it for the hell of it).
Any thoughts?
Edit, I get the same problem on Eclipse 4.4 (Luna). I found the logs for the errors and the error is:
!ENTRY org.eclipse.linuxtools.oprofile.core 4 0 2014-10-27 12:33:07.200
!MESSAGE opreport process error output: warning: /no-vmlinux could not be found.
I have created a simple Hello.jsp program in my eclipse(juno).When I tried to run this jsp file by run on server,getting below error
problem occurred,
'Publishing to Tomcat v6.0 Server at localhost' has encoured a problem
Publishing failed with multiple errors
Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30730.jsp.
Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30731.MF.
Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30732.xml.
In the error log, getting the below details
!ENTRY org.eclipse.jst.server.tomcat.core 4 0 2013-12-11 22:46:11.654
!MESSAGE Publishing failed with multiple errors
!SUBENTRY 1 org.eclipse.wst.server.core 4 0 2013-12-11 22:46:11.654
!MESSAGE Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30730.jsp.
!SUBENTRY 1 org.eclipse.wst.server.core 4 0 2013-12-11 22:46:11.654
!MESSAGE Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30731.MF.
!SUBENTRY 1 org.eclipse.wst.server.core 4 0 2013-12-11 22:46:11.654
!MESSAGE Could not replace with temp file C:\workspace.metadata.plugins\org.eclipse.wst.server.core\tmp0\temp\tmp30732.xml.
I have deleted eclipse & tomcat server, then reinstalled again. But still getting the same error.I tried by selecting server location as use custom location and giving different workspace path. But nothing works.
I'm using eclipse Juno, apache tomcat-v6.0.37, jdk 1.6
Can anyone please help me on this issue? Thanks in advance
I have created a new eclipse workspace in another directory and kept the server also inside the workspace. Now it is working for me.The solution is we should have the server and eclipse workspace in same file system.
Any of those worked for me. I deleted the temp folder from my tomcat installation and removed also the project folder (the one that was causing the problem) from the wtpweapps folder, and it worked.
I'm trying to develop an plugin for SAP Design Studio using the SDK (which uses eclipse...) and set it up like the documentation says.
When I try to run the plugin via eclipse, I get the following error:
!ENTRY org.eclipse.osgi 2 0 2013-10-23 14:18:48.915 !MESSAGE One or
more bundles are not resolved because the following root constraints
are ot >resolved: !SUBENTRY 1 org.eclipse.osgi 2 0 2013-10-23
14:18:48.915 !MESSAGE Bundle
initial#reference:file:D:/workspace/com.sap.sample.coloredbox/
was not resolved. !SUBENTRY 2 com.sap.sample.coloredbox 2 0 2013-10-23
14:18:48.915 !MESSAGE Missing required bundle
com.sap.ip.bi.zen.rt.components.sdk_0.0.0.
So something the bundle "com.sap.ip.bi.zen.rt.components.sdk_0.0.0" seems to be missing - but I don't know where it should come from...
A few weeks ago I've installed the SDK on another machine, and there it's running fine.
I've noticed that in Eclipse (with the sample plugin selected) under "Project->Propertires->Run/Debug Settings", then edit a Launch Configuration, under the fieldset "Program to run" the point "Run a product" is grayed out and has an attention mark which has following hint text:
"A product with thus name cannot be found in any required bundle. This
launch may fail to start as expceted unless there is an avaialable
IProductProvider that can supply this product".
On the other machine where the SDK is running, the point is not grayed out and the product "com-sap.ip.bi.zen" is selected.
So the problems seems to be very clear - I only don't know how to resolve it... :/
Thanks for any help!
ensure that your plug in design studio target path is valid (preferences -> plug-in development -> target platform).
In my case (win 7 32 bit) I needed to fix the design studio path IMMEDIATELY after pulling in the sdk reference (preferences -> XML -> XML Catalog). Once eclipse has resolved this it apparently will not do so again if corrections are made.
Finally I could solve the problem with creating a new workspace.
I'm continually getting the following error under Eclipse Galileo while trying to install the WTP Web Page Editor plugin:
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:54)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:76)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:29)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
One blog said Eclipse Galileo doesn't play well with Java 1.6 (what??), so I've tried running Eclipse with Java 1.5 but that hasn't helped. Has anyone else had this problem and been able to get around it?
Edit BTW, below the error in the error log it also says
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Install, operand=null --> [R]javax.mail 1.4.0.v200905040518, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
You can try to follow the various suggestions mentioned in the bug 277242
Also check your eclipse.ini:
More generally, the error you're seeing can happen when we cannot read "-startup" since we use this to position the install.area.
As suggested by Jelle van Geuns in the comments (and confirmed by Halfstop):
I found that one MacOS there are two folders (MacOS and Eclipse) with two separate sets of configuration files.
Each had an 'org.eclipse.equinox.launcher' startup jar in the plugins sub-folder, but with slightly different versions.
The Eclipse executable resides in the MacOS folder.
But the eclipse.ini there was set up to look for the startup jar under Eclipse/plugins, but with the wrong version.
Solution that worked for me was to copy both versions of the startup.jar to both the plugins sub-folders.
Halfstop confirms:
I copied all of the what was in Eclipse to the MacOS directory and this solved it.
I just ran into this problem today. The answer provided by VonC et al helped to locate the problem but didn't quite fix it.
In my case, the location specified in -startup within the MacOS/eclipse.ini was incorrectly looking in the ../Eclipse/plugins folder rather than the ../MacOS/plugins folder.
I corrected the path and the error went away.
try to chown -R your_user_name:your_user_name /path/to/eclipe
Try edit
Eclipse/configuration/config.ini.
Make sure osgi.instance.area.default= value is right workspace. This works for me.
I'm not sure if the above answers adequately resolve this issue. I've found that, with a number of our eclipse derivative RCP products, that on some linux machines plugins will fail with log entries like this one:
!ENTRY org.eclipse.equinox.p2.engine 4 4 2017-02-23 12:00:49.492
!MESSAGE An error occurred while installing the items
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492
!MESSAGE session context was:(profile=TIBCOBusinessStudio-4.0, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.tibco.eclipse.p2.installer 1.1.3.20161130, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:59)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:75)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:32)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:38)
at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:183)
at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:95)
at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:47)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:159)
at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
The reason this happens (I suspect) is that the actual file name of the config file is compared with the absolute name by the lazyloader. In my case the home dir is a symlink, so the two names don't match. The resolution was to edit the eclipse.ini (or whatever yours is called) and ensure that all the paths referencing the eclipse home dir are fully qualified and do not rely on symlinks.
I developed one plugin(RMP) in eclipse 3.3.2 where i am creating menu items dynamically. I ran the application and it is working fine and am able to see the menu items created dynamically.
Now I exported this plugin(RMP). I added this in plugin folder of eclipse 3.4 installation. Now I launched eclipse and I am able to see all the functionalities implemented in my plugin(RMP) but the menu items created dynamically are invisible. When i click on menu, nothing is coming.
Pls find the error log below for more information. I took this log from my workspace -> .metadata folder.
Log:
!ENTRY org.eclipse.ui.workbench 2 0 2009-03-30 11:59:23.266
!MESSAGE A handler conflict occurred. This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2009-03-30 11:59:23.267
!MESSAGE Conflict for 'AUTODCTOOL':
HandlerActivation(commandId=AUTODCTOOL,
handler=ActionDelegateHandlerProxy(null,com.ericsson.eadt.apstoolsintegrator.actions.APSToolAction),
expression=AndExpression(ActionSetExpression(APSToolsIntegrator.APSSystemFullSet,org.eclipse.ui.internal.WorkbenchWindow#166c114),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#166c114)),sourcePriority=16640)
HandlerActivation(commandId=AUTODCTOOL,
handler=ActionDelegateHandlerProxy(null,com.ericsson.eadt.apstoolsintegrator.actions.APSToolAction),
expression=AndExpression(ActionSetExpression(APSToolsIntegrator.APSSystemFullSet,org.eclipse.ui.internal.WorkbenchWindow#166c114),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#166c114)),sourcePriority=16640)
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2009-03-30 11:59:23.267
!MESSAGE Conflict for 'BTIDRIVER':
HandlerActivation(commandId=BTIDRIVER,
handler=ActionDelegateHandlerProxy(null,com.ericsson.eadt.apstoolsintegrator.actions.APSToolAction),
expression=AndExpression(ActionSetExpression(APSToolsIntegrator.APSSystemFullSet,org.eclipse.ui.internal.WorkbenchWindow#166c114),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#166c114)),sourcePriority=16640)
HandlerActivation(commandId=BTIDRIVER,
handler=ActionDelegateHandlerProxy(null,com.ericsson.eadt.apstoolsintegrator.actions.APSToolAction),
expression=AndExpression(ActionSetExpression(APSToolsIntegrator.APSSystemFullSet,org.eclipse.ui.internal.WorkbenchWindow#166c114),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#166c114)),sourcePriority=16640)
Requesting help in this regard,
Thanks in advance.
Snehal.
Try launching your eclipse3.4 with the -clean option.
If a -clean is not enough, the problem lies in the definition of com.ericsson.eadt.apstoolsintegrator.actions.APSToolAction.
If it is an action set, check its definition: a keybinding used might be in conflict with legacy eclipse3.4 keys definition.