Some time ago my company migrated our Windows profiles and created new ones. I had an old installation of Eclipse Neon on the old profile.
I'm now trying to install a fresh copy of the latest eclipse and it always fails because it's trying to create folders for the old Windows profile, that doesn't exist.
Here's one of the errors it reports:
ERROR: org.eclipse.equinox.p2.artifact.repository code=1003 Unable to write to repository: file:/C:/Users/oldUser/.p2/pool.
java.io.IOException: Failed to create directory C:\Users\oldUser\.p2\pool\plugins.
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getOutputStream(SimpleArtifactRepository.java:1023)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:280)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:225)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:155)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:759)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
The folder C:\Users\oldUser does not exist anymore. Why isn't the installer installing it for the user I'm actually logged in as?
As far as I can tell, none of the old Eclipse Neon stuff still exists.
Turns out it had to do with a feature called "Bundle Pools". The installer, by default, has this feature turned on - it somehow knew / remembered the previous Neon installation and was trying to write to that. Turning off the "Bundle Pools" feature during the install allowed the setup to finish.
Related
I installed notepad++ recently which came with the new plugin admin. After that I am unable to install new or update existing plugins.
Any idea what the issue could be? I tried "Run as administrator"and also pasting the dll directly to C:\ProgramData\Notepad++\plugins but nothing works.
Here are the app details.
Notepad++ v7.6.1 (64-bit)
Build time : Dec 12 2018 - 01:22:05
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : ON
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll
1) to install plugins manually copy the dlls in folder \Plugins\ but stored in individual folders (having same name than file.dll)
note. plugin Admin place for plugins is C:\ProgramData\Notepad++\plugins
2)Plugin Admin, if you can see this entry in Menu, I understand you have the Setup version and during installation "Don't use %APPDATA%" checkbox was disabled.
You have to:
Tick the checkboxes of plugins to install
Click "Install"
Click "YES" when asking about restart the app
if this doesn't work, are you receiving any message?
I was able to get this working with a 32-bit version. I was trying to install a 32-bit compatible plugin and that did not work with a 64-bit version.
I had to manually copy the dll to C:\ProgramData\Notepad++\plugins.
I had similar problems, mine were caused by my company introducing WIndows 10 (64bit) and enforcing UAC.
Problem was, that proxy-information was not persisted in NPP, I also couldn't specify my proxy-credentials in the Updater-Proxy-dialog.
Solution was not using %APPDATA% during installation, then run NPP in administrator-mode (now proxy-credentials are persisted).
After restarting NPP in non-administrative mode, Plugin-Admin worked like charm.
Did a quick write-up here how to remedy this:
https://blog.2smart4u.de/2019/07/notepad-windows-10-uac-plugin-nightmare.html
the default plugin folder has the dll. if you get it installed on another machine and can create the plug can copy the folder from that location, go back to old location, close the program then drop the folder in the default location then open up u should now see the plug in.
I'm trying to install Netbeans 8.2 Java EE, but whenever I start the installer it quits after configuring it. I am trying to install it on Windows 10 64-bit.
This is not going to make sense at all, but do you happen to have the "God Mode" item on your desktop? Take it off the desktop (delete it, move it somewhere else, whatever). I have no idea why, but it worked for me: I found the solution in this bug report - https://netbeans.org/bugzilla/show_bug.cgi?id=269988
I do hope this helps you, too.
This is an Java issue, which was came up due to recent windows 10 update, that started treated differently for GodMode folder/shortcut.
This has been already fixed - https://bugs.openjdk.java.net/browse/JDK-8179014
You can verify the fix in early access build of JDK8 update 152, which is available here
We have verified the issue only with GodMode, do let us k now if there are any other scenarios that can cause such similar issues.
I'm adding this because: I had a different issue which I was unable to find addressed anywhere, this question appears near the top of a web search for "NetBeans 8.2 ee won't install on Windows 10", and someone else may have the problem I had.
My NetBeans install was almost immediately crashing with the following error:
An unexpected exception happened in thread main
Exception: javax.xml.parsers.FactoryConfigurationError: Provider for
class javax.xml.parsers.DocumentBuilderFactory cannot be created
In my Windows 10 System Properties -> Environment Variables -> System Variables, I had a previously created _JAVA_OPTIONS variable values using -Xbootclasspath/a to append some jar files to the end of the bootstrap class path. These files are used with some work I'm doing with the Oracle BI Publisher plug-in for Microsoft Word.
As soon as I renamed the _JAVA_OPTIONS variable to something else, my NetBeans installation started normally and completed with no issues.
After NetBeans installation, I reset the name of this variable back to _JAVA_OPTIONS, and discovered that the values I have for this System Variable cause NetBeans launch to crash. (Which does not completely make sense to me since I am only appending these files/classes to the class path, and not overwriting.)
Regardless, I'll have to go back to the drawing board for my work with the BI Publisher plug-in; but at least I can use NetBeans now!
Uninstall any Java installations along with NetBeans, and install Java with NetBeans (bundle) from the Oracle website.
I had the same issue, and then installed the bundle, works perfectly.
So very weird, first time I ever saw this, problem install STS version 3.8.3-release on Macbook Pro running mac osSerria v10.12.3. Here's what's I do:
Down load the STS distro spring-tool-suite-3.8.3.RELEASE-e4.6.2-macosx-cocoa-x86_64.tar.gz from https://spring.io/tools/sts/all
Move the zip file to my Applications folder
Extract the distro. This creates the sts-bundle folder, and; under that, the STS programs exists.
I then just run STS. Since this is a first-time I do get the pop-up for selecting the default workspace. I change it to where I want the workspace and I also check the "Don't ask again".
Install some plug-ins, do work, everything is normal.
I can exit the app throughout the day and, when I go back in all is cool.
Now...the problem...
1. Shutdown the laptop for the day. This is to say I select Apple->Shut Down..
2. The next day I come in, boot-up the laptop.
3. Open Applications and select STS and run STS.
At this point, I get the "Select default workspace" popup again...all my preferences, and installed plug-ins are forgotten, and it's like I'm running the application again for the first time?? It is especially weird that any plug-ins I installed are also forgotten??
I have completely removed STS, and reinstalled several times and it is pretty consistent. Also, I have installed STS on several iMac desktops without issue. This smells like a permissions problem but not errors just...all customized preferences are simply gone.
Any ideas would be greatly appreciated.
The answer to this is App Translocation, which is done by OSX. For details, take a look here, we analyzed this in detail:
STS.app on Mac 10.12.1 always creates a new org.springsource.sts folder in .eclipse
I've downloaded and installed STS 3.8.2 on my Mac (10.12.1). Each time the STS.app file is launched, it creates a new org.springsource.sts_3.8.2.RELEASE_########_macosx_cocoa_x86_64 folder under the hidden .eclipse folder (the hashes are there because I have MANY of the same folder with the numbers in the hash area being the only difference). In doing so, the default workspace and all plugins I installed the last time it was running are wiped out (because they exist in the previous #### folder).
I've tried installing the previous 3.8.1 and 3.8.0 version, but they are doing the same thing. My previous STS install started at 3.7 and has been upgraded to 3.8.1, but will not update anymore because of update errors that I can't seem to fix (none of the StackOverflow "fixes" have worked for me).
Is there a way to have STS not create a new folder (instance) in the .eclipse folder each time it launches? If so, how?
This got reported to STS and is documented here:
https://issuetracker.springsource.com/browse/STS-4406
The corresponding bug at Eclipse is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=507328
To cut a long story short:
This is caused by macOS Sierra Gatekeeper App Translocation, a security feature that moves the app into a private read-only location for security reasons. Therefore Eclipse/STS creates a folder for its configuration in that location that you described above.
Since macOS Sierra does the app translocation again after every restart, Eclipse/STS doesn't know anything about the "old" configuration area anymore and creates a new one. As far as I can see, there is no way for Eclipse/STS to distinguish between a separate install and a newly translocated app... :-(
The workaround is:
A) Move STS.app into a different location on your disc after
unpacking the tar.gz archive (using the Finder, not the command
line). If you move it to "Applications", for example, everything
works as before (no app translocation happens in that case).
B) You could also start Eclipse/STS by clicking on the Executable (in
STS.app/Contents/MacOS). That also doesn't cause app translocation
and therefore everything is fine.
As this bug — alternatively unfortunate side-effect of Apple security measures — still exists in STS 3.9.8 (I assume also in 3.9.9) and the Eclipse bug report in the previous answer is closed as a duplicate of Workspace Preferences Do Not Persist on MacOS Sierra that, while being marked as "solved, actually in itself actually do not solve this dislocation issue — in that moving the app to /Applications or having a signed DMG, both making no difference — the info missing is that one can turn off App Dislocation on an app by app basis by using the "xattr" command in the Terminal, that works upon extended file attributes.
Use the command
sudo xattr -r -d com.apple.quarantine /Applications/sts.app
where -r makes the command recursive for all app contents (macOS apps being folders) and -d deletes the particular attribute at the given path.
To verify a successful result simply run
sudo xattr /Applications/sts.app
The successful result you want is a new prompt line. If you get "quarantine" on there you were not successful.
Note that, I could only test this in macOS 10.12.6
I'm using latest Jenkins (v 1.590) LOL, but Jenkins official site say: 1.588. I'm 200% sure that I did see 1.589 and 1.590 few days back on Jenkins official download site(when I wanted to upgrade Jenkins to newer version).
This is what I see at the bottom of my Jenkins instance page.
Page generated: Nov 19, 2014 12:07:51 PMREST APIJenkins ver. 1.590
Now, the issue I'm facing is: Since I upgraded few of the plugins and Jenkins itself recently, some of the jobs are missing (I see this can happen during upgrades but upgrading to latest Jenkins should fix it and I'm two steps ahead of what Jenkins has on their official site, right):
I go to Manage Jenkins, Manage Plugins, Go to Available tab, check mark bunch of plugins to install (Artifactory, Maven project plugin etc ) and restart Jenkins using Jenkins GUI interface (which happens automatically once plugins are downloaded/installed in Jenkins GUI). After the restart, I do the same to see whether the plugin is now showing under "Installed" tab or not, but to my luck, it's still showing under "Available tab" and is NOT listed under "Installed" tab. If I open an existing job's configuration OR create a new job, the features available due to installed plugins are NOT visible i.e. if I installed Maven Project Plugin, I don't see an option to create a Maven style(2/3) project job while creating a new job.
I see valid .jpi files for respective plugins in plugins folder in JENKINS_HOME and there are some .pinned files as well. I have tried this a couple of times but the plugins are not visible once installed. Installation doesn't give any error during the whole operation.
Jenkins system log file (upon Jenkins restart) is attached (NOTE: Use slow download button to see/download this log file).
Download at SpeedyShare
or
[code]http://speedy.sh/x6vd8/Jenkins.System.Log[/code]
Issue was with the plugins permissions and expanded folders.
If you see under the plugins folder, you'll see .jpi or .hpi files (Jenkins jpi and Hudson hpi).
If I have awesomeplugin.jpi then there will be a folder called awesomeplugin.
Using Slav's hint, I ran bunch of checks and found out of 70+ plugins that I had installed, few of them somehow got "root" and "root" as their owner and group for their .jpi files and corresponding folder.
Now, The best solution one can try (the safest approach) is to chown -R yourvalidjenkinsuser:yourvalidgroup * and chmod -R 755 * as root. Before doing this, stop/shutdown jenkins.
I went even a step further, I first took backup of config files / whole jenkins JENKINS_HOME folder. Then I went to plugins folder and remove all .jpi corresponding folders using root account or as the owner of those folders (NOTE, I didn't delete the .jpi files). Then, I ran the above two commands (chown/chmod) and started Jenkins.
OUTCOME:
when I'm going to Jenkins > New item (to create a new job), Shenzi, all different types of jobs options are showing up (which included the Maven2/3 type job which I found got missing and few others like "Multi-configuration project" and Multijob Project job type.. all were missing and now they are showing up.
OK, I also checked one of the old job, went to its job's configuration and Shenzi!! I now see all the features there i.e. (Promoted Job plugin feature "Promtoe builds when.." check box. This feature which I configured sometime back, got missing but now it's showing up again.
Few of the Maven jobs that I created in past with Maven Release Plugin and Release Plugin POC work had bunch of steps in it. I found there was nothing in the Build step (after this whole mess), but after the above solution, I now see everything is back. I can see the configurations and build steps populated as they were set.
I hope this can help someone facing similar issue.
Still, I don't know why my Jenkins version is 1.590 (which Jenkins updated recently in automatic fashion) and Jenkins site today says, their latest Jenkins artifact is version 1.588 (seems like a mystery).
When you say "valid .hpi files", did you actually test that they are valid? You should be able to rename them to .zip and extract as a valid archive. An issue I face a lot is the network layer filtering system that we have in the office. It intercepts Jenkins's calls sometimes with the filtering system's login page, instead of whatever internet resource was being loaded.
If your .hpi files are not valid zip archives, open them in a text editor, and see if they are in the form of an html page/response of some kind.