I am using Eclipse Luna Service Release 1 (4.4.1)
When I try to install new software
It gives some error message like Cannot complete the request. This installation has not been configured properly for Software Updates.
And my error log says
eclipse.buildId=4.4.1.M20140925-0400
java.version=1.7.0_75
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_IN
Framework arguments: -product org.eclipse.epp.package.standard.product
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.standard.product
org.eclipse.equinox.p2.ui.sdk
Warning
Mon May 11 14:35:07 IST 2015
Could not locate the running profile instance. The eclipse.p2.data.area and eclipse.p2.profile properties may not be set correctly in this application's config.ini file.
I came across similar problems in
How to enable Software Update in an Eclipse product?
and Getting the message "Cannot start the update ui..." when trying to run the update UI in Eclipse
but it didnot solve my problem
I hit this same error (Eclipse Mars).
Shutting down all Eclipse instances and starting with eclipse.exe -clean fixed it.
Bug 378568 mentions:
Looks like the configuration of your eclipse is damaged.
Check the value of 'eclipse.p2.profile' and 'eclipse.p2.data.area' in config.ini, then check whether the specified profile can be found from path 'eclipse.p2.data.area'.
<eclipse.p2.data.area>\org.eclipse.equinox.p2.engine\profileRegistry
Removing those files (in the folder eclipse.p2.data.area) and relaunching Eclipse should help fix the issue.
Although FaithReaper mentions in the comments:
Removing the eclipse.p2.data.area folder prevents Eclipse from launching.
In my case it is C:\Users\<my.user.name>\.p2
The discussion mentions the error:
An internal error occurred during:
"Loading bundle:
/eclipse/configuration/org.eclipse.osgi/1304/0/.cp/bundles/php.ruble".
org.eclipse.osgi.internal.framework.EquinoxConfiguration$1
cannot be cast to java.lang.String
This is mentioned in this answer (and this one) as a patch to be applied (see bug 445122: ClassCastException received when System.getProperties().store() runs on 4.4.1)
Just add the following lines to eclipse.ini:
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dosgi.configuration.area.default=null
-Dosgi.user.area.default=null
-Dosgi.user.area=#user.home
-Dosgi.instance.area.default=null
It worked when I put the full eclipse folder (containing the executable) at the root of the harddrive like :
C:\eclipse
Same for the workspace.
Related
I have tried to install the TeXLipse extension in Juno Eclipse, running on Ubuntu 12.04.
The installation goes off without a hitch however when I choose the project creation wizard TeXLipse is not there as an option. It is also not showing up in the Windows > Preference section of eclipse.
Has anyone else experienced this and have a suggestion on how to get this to work. I have googled around and other people have gotten it to work with Juno. I am just not sure what I am missing.
Thanks
Edit: Solution
I want to impart some details. I have the stock Eclipse install for Eclipse on Ubuntu. I then did an update where I simply replace the eclipse install located in /usr/lib/eclipse.
You can Google around for specifics.
To figure out what my system was doing I did two things.
Located in the ~/workspace/.metatdata folder is a file called .log. At the terminal I ran tail -f ~/workspace/.metatdata/.log so that I could watch the log files for any errors as I did the installation.
I ran eclipse from the terminal $> eclipse to see any errors were produced.
My first error was that eclipse could not fine ~/.eclipse file/directory when I ran eclipse. So I simply created this directory in my home folder and this error went away. I tried to install the plugin and I got a new error posted to the .log file:
!SESSION 2013-01-31 11:21:39.559 -----------------------------------------------
eclipse.buildId=M20120914-1800
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.equinox.p2.engine 4 4 2013-01-31 11:23:38.266
!MESSAGE An error occurred while committing the engine session for profile: epp.package.jee.
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-01-31 11:23:38.266
!MESSAGE
!SUBENTRY 2 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-01-31 11:23:38.266
!MESSAGE Error saving manipulator.
!STACK 0
java.io.FileNotFoundException: **/usr/lib/eclipse/eclipse.ini** (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:209)
at java.io.FileOutputStream.<init>(FileOutputStream.java:160)
at java.io.FileWriter.<init>(FileWriter.java:90)
at
org.eclipse.equinox.internal.frameworkadmin.equinox.EclipseLauncherParser.save(EclipseLauncherParser.java:321)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.save(EquinoxManipulatorImpl.java:378)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.save(LazyManipulator.java:97)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseTouchpoint.saveManipulator(EclipseTouchpoint.java:61)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseTouchpoint.commit(EclipseTouchpoint.java:137)
at org.eclipse.equinox.internal.p2.engine.EngineSession.commit(EngineSession.java:123)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:93)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174)
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:53)
The installer wanted to update the /usr/lib/eclipse/eclipse.ini. I changed the permissions on this to write all (the alternative is to run eclipse as root which I didn't want to do).
I uninstalled the plugin and re-installed it and now it works as intended. I hope this helps someone else. Don't forget to reverse the permissions after.
Eclipse seems to need write permissions to the place where you installed it. How I see it, this leaves you with two options:
Install (i.e., extract) Eclipse to a folder you own, for example your home folder.
If you installed Eclipse to /opt/eclipse owned by root, you also have to install plugins as root.
This question describes the same problem under Windows. This (German) website suggests option 2 from the above as solution.
How do I resolve the above reported error message? Additional details are given below:
Exception Stack Trace
java.lang.NullPointerException
at org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:48)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2843)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1878)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:3128)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2691)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2855)
at org.eclipse.jdt.internal.core.ClasspathChange.generateDelta(ClasspathChange.java:220)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2052)
at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2353)
at org.eclipse.wst.jsdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2153)
at org.eclipse.wst.jsdt.internal.core.JavaModelManager.getJsGlobalScopeContainer(JavaModelManager.java:1530)
at org.eclipse.wst.jsdt.core.JavaScriptCore.getJsGlobalScopeContainer(JavaScriptCore.java:1319)
at org.eclipse.wst.jsdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2740)
at org.eclipse.wst.jsdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2019)
at org.eclipse.wst.jsdt.core.JavaScriptCore.initializeAfterLoad(JavaScriptCore.java:2655)
at org.eclipse.wst.jsdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:32)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Session Data
eclipse.buildId=I20120608-1400
java.version=1.7.0_08-ea
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/ravisankars/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/ravisankars/.eclipse_keyring -showlocation
One thing I did (though I recommend uninstalling and re-installing your plugins first as previously posted by #Rajkumar) is to remove the builder causing the issue. MyProject -> Properties -> Builders ...[Troublesome Builder]... Remove.
It is a short run solution, you are only circumventing the real issue, but for me, it did what I needed it to for the time being.
Quite a few things had happened since I first installed Eclipse, like (a) installing / uninstalling plugins (b) upgrading the IDE without correspondingly upgrading the workspace. Since the history has become complex, troubleshooting also got trick. Fresh installation along with importing the code base again, fixed the issue for me.
Problem like happens if you have to many resources file like java scripts in your eclipse project. The solution is to remove the java script nature from project facets or disable the java script validation.
Well, before you go into all the trouble of uninstalling and installing again; if you haven't done any special action with your plug-ins, you may want to try the following which is fast and simple:
Close the project(s)
Open the project(s)
Restart eclipse
For me after this it is working. This is solving a lot of unaccepted issues that may occurred with older eclipse versions too.
I am getting below error when trying to deploy war file on Tomcat 7.0.28 server. My Eclipse is Eclipse Java EE IDE for Web Developers.Version: Indigo Service Release 2 Build id: 20120216-1857. I would appreicate if anyone can provide a solution/fix? Is it related to version of eclipse or tomcat compatability? Thanks.
java.lang.NullPointerException
at java.io.FileInputStream.<init>(Unknown Source)
at org.eclipse.wst.server.core.util.PublishHelper.copyFile(PublishHelper.java:501)
at org.eclipse.wst.server.core.util.PublishHelper.publishDelta(PublishHelper.java:435)
at org.eclipse.wst.server.core.util.PublishHelper.publishDelta(PublishHelper.java:459)
at org.eclipse.wst.server.core.util.PublishHelper.publishDelta(PublishHelper.java:459)
at org.eclipse.jst.server.tomcat.core.internal.PublishOperation2.publishDir(PublishOperation2.java:141)
at org.eclipse.jst.server.tomcat.core.internal.PublishOperation2.execute(PublishOperation2.java:82)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.performTasks(ServerBehaviourDelegate.java:1290)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:933)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
eclipse.buildId=M20120208-0800
java.version=1.6.0_32
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
If you using Eclipse or Myeclipse IDE's, Clean all projects like Project --> Clean --> Clean all projects --> Ok. Now its working fine
Following this thread lead me to a solution http://www.eclipse.org/forums/index.php/m/526327/
It seems that the deployment config file for your application has become incorrect.
What happened for me is that if I modified my server options and unchecked "Serve modules without publishing" the server would start. With it check I got the error you mentioned.
For me the problem is that eclipse could not find my web.xml. My solution was that I had to go to my project settings and remove and add the reference to my webapp folder under Deployment Assembly. This brought up a dialog for the location of my deployment description. After Eclipse had that a restart got everything in order.
Seems to be a bug. Here is the workaround;
When adding a new server, do not add any web application to the server. Just add a server with no web module. After server was added, right click on server and "Add and Remove". This should now work.
had the same problem with Eclipse Neon 2 (4.6.2) and Tomcat 8.5. Workaround is working. Add a server, but do not add application to it. Then run application "Run on server" and it will start working. Also need to say that I deleted all Maven repository and restarted Eclipse. After restart Maven downloaded all dependencies. I did not like to delete repository, but it seems it is also important part for troubleshooting.
I faced the same issue. Just delete the server alone. Add the new server and projects into the server. Clean the tomcat work directory. Then start the server it will work fine
I am very new to the Maven. I am trying to install m2e plugin in my Eclipse (eclipse-jee-helios-SR1-win32) from the Eclipse Marketplace. My Eclipse folder is in c:\ (c:\eclipse). It downloads and installs it properly (at least it looks so!) and then ask to restart Eclipse. I do restart it. But as soon as it restarts, it starts downloading some stuff and I get the following error:
eclipse.buildId=M20100909-0800
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
Error
Fri May 27 11:17:41 EDT 2011
Unable to update index for central|http://repo1.maven.org/maven2
java.io.IOException: An existing connection was forcibly closed by the remote host
at org.maven.ide.eclipse.internal.index.AsyncFetcher$PipedErrorInputStream.checkError(AsyncFetcher.java:181)
at org.maven.ide.eclipse.internal.index.AsyncFetcher$PipedErrorInputStream.read(AsyncFetcher.java:188)
at java.io.PipedInputStream.read(PipedInputStream.java:361)
at java.io.InputStream.read(InputStream.java:85)
at java.util.Properties$LineReader.readLine(Properties.java:418)
at java.util.Properties.load0(Properties.java:337)
at java.util.Properties.load(Properties.java:325)
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:498)
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.access$100(DefaultIndexUpdater.java:74)
at org.sonatype.nexus.index.updater.DefaultIndexUpdater$IndexAdaptor.setProperties(DefaultIndexUpdater.java:780)
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:954)
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:138)
at org.maven.ide.eclipse.internal.index.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1072)
at org.maven.ide.eclipse.internal.index.NexusIndexManager.updateIndex(NexusIndexManager.java:1025)
at org.maven.ide.eclipse.internal.index.NexusIndexManager$1.run(NexusIndexManager.java:632)
at org.maven.ide.eclipse.internal.index.IndexUpdaterJob.run(IndexUpdaterJob.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:200)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:322)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Does anyone has ANY idea what is this? I repeated the process thrice, repeated on fresh installation of Eclipse, same problem. My colleague is using same version of Eclipse and has done the same process. He was able to install m2e in < 1 minute! This is so frustrating!
EDIT 1:
I have configured Proxy Settings in Eclipse Network Connections and those settings are working fine for my colleagues. So I guess it is not a proxy issue.
Although the Public Maven address itself isn't browsable anymore recently, this is more likely due to a Network Connections settings in your Eclipse.
See this answer to set your proxy if you have one, and more generally, check the "Network Connections" settings of your Eclipse's colleague to ake sure you have the same.
For information/archive, regarding the browse status of http://repo1.maven.org/maven2:
The raw browsing ability was originally removed to prevent automatic web crawler/scraper activity from de-stabilizing the Central servers.
Some of that ability has been returned.
It is currently possible to browse at levels deeper than the root, /org, /com, and /net.
So, if you try to navigate to http://repo1.maven.org/maven2/org, for example, you will see a static page with a link to the appropriate Browse view on http://search/maven.org.
However, if you go even one level deeper, to http://repo1.maven.org/maven2/org/apache, the standard directory browse functionality will be in place.
Found simple solution. Just did an update for Eclipse and it worked!
I have a problem downloading new software via the "Install New Software..." dialog of Eclipse Helios.
It used to work a few weeks ago, but now I get the following error when I try to visit the official Helios site.
org.eclipse.equinox.p2.core.ProvisionException
Unable to read repository at http://download.eclipse.org/releases/helios.
This is what I get in the error log:
eclipse.buildId=M20110210-1200
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_DK
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.java.product
Error
Thu Apr 21 12:56:41 CEST 2011
Unable to read repository at http://download.eclipse.org/releases/helios.
org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.eclipse.org/releases/helios.
at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:137)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:746)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.ui.ProvisioningUI.loadMetadataRepository(ProvisioningUI.java:388)
at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:120)
at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getRepository(MetadataRepositoryElement.java:109)
at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:103)
at org.eclipse.equinox.internal.p2.ui.QueryProvider.getQueryDescriptor(QueryProvider.java:54)
at org.eclipse.equinox.internal.p2.ui.model.QueriedElement.fetchChildren(QueriedElement.java:102)
at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.fetchChildren(MetadataRepositoryElement.java:72)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:34)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.io.IOException: http://download.eclipse.org/releases/helios is not a valid repository location.
at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:113)
... 15 more
I have used wireshark to see exactly what eclipse does when I request the update site, and I have discovered that it does a HTTP GET request on the host download.eclipse.org, for the page "/releases/helios/p2.index" (without quotes) and that it gets a 404 error from the webserver.
This is what I get when I navigate to http://download.eclipse.org/releases/helios/p2.index as well.
Does anyone have the same problem? Do I have something in my settings mixed up? Does anyone have an idea to solve my problem? or do you guys need some more info?
The bug 341665 presents a similar case and has the workaround of using a mirror:
I found where the problem is. I'm here in China, and I can't access
http://www.gtlib.gatech.edu/pub/eclipse/releases/helios/, where http://download.eclipse.org/releases/helios/compositeContent.jar is redirected to, because our government has blocked the access to http://www.gtlib.gatech.edu/*
So please change a repository to help us developers in China. Thank you.
[reply] [-] Comment 5 shining366#gmail.com 2011-04-15 20:47:08 EDT
I find a workaround:
use http://mirror.neu.edu.cn/eclipse/releases/helios/ instead of http://download.eclipse.org/releases/helios
Note, as described in bug 325299:
There is an ordering for the files that we look for when we connect to a server:
compositeContent.jar
compositeContent.xml
content.jar
content.xml
site.xml
add this line to
eclipse.ini
-Djava.net.preferIPv4Stack=true