search

pombreda / windows-package-manager

Automatically exported from code.google.com/p/windows-package-manager
0 stars 0 forks source link

Never run the Java installer #411

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.install jdk
2.files get copied to windows/system32
3.breaks java_home interpretation at command line

What is the expected output? What do you see instead?
echo %JAVA_HOME% is correct
echo %PATH% is correct
java -version is incorrect and does not match above

What version of the product are you using? On what operating system?
windows 7

Please provide any additional information below.
Renaming or removing files from /windows/system32 fixes the problem. Thanks

Original issue reported on code.google.com by cmtopi...@gmail.com on 27 Oct 2014 at 4:49

GoogleCodeExporter commented 9 years ago 
AFAIK JDK installer does not change JAVA_HOME or PATH. You probably have 
another application installed that changed these variables.

c:\windows\system32\java.exe is just a simple 200 KiB big executable that 
searches for the newest Java installed on the machine and executes it. It is 
part of the JRE.

=> Npackd does nothing special here. It is the normal JDK behavior that you 
would also get if you would install it manually.

Original comment by tim.lebe...@gmail.com on 28 Oct 2014 at 5:33

GoogleCodeExporter commented 9 years ago 
How does it find the newest installed java?

On Tue, Oct 28, 2014 at 12:33 PM, <windows-package-manager@googlecode.com>
wrote:

Original comment by cmtopi...@gmail.com on 28 Oct 2014 at 10:04

GoogleCodeExporter commented 9 years ago 
When I installed JRE 64 bit from npackd c:\windows\system32\java.exe got
set to look for that install.

The way I install jdk I download and unzip I don't use the installer.

Once I removed c:\windows\system32\java.exe applications were able to find
jdk I had set on path as java_home.

Application in question is Spring Tool Suite.

Original comment by cmtopi...@gmail.com on 28 Oct 2014 at 10:11

GoogleCodeExporter commented 9 years ago 
1. c:\windows\system32\java.exe find the JREs via the registry. See 
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft for more details
2. I am not sure how I could help you as you installed the software without 
Npackd.

Original comment by tim.lebe...@gmail.com on 29 Oct 2014 at 9:45

GoogleCodeExporter commented 9 years ago 
? I installed JRE 64 bit from npackd #427. Npackd maintained apps have an
available version, right?

How do I tell what npackd maintained installs are in ui vs. non-npackd
maintained?

On Wed, Oct 29, 2014 at 4:45 PM, <windows-package-manager@googlecode.com>
wrote:

Original comment by cmtopi...@gmail.com on 29 Oct 2014 at 10:13

GoogleCodeExporter commented 9 years ago 
let's go back to the initial question. Neither JDK installer nor Npackd modify 
JAVA_HOME or PATH. The behavior you see is normal for the JDK. It's not an 
error in Npackd.

Original comment by tim.lebe...@gmail.com on 31 Oct 2014 at 6:34

GoogleCodeExporter commented 9 years ago 
Understood. JDK installer modifies windows/system32 and java apps use what
is set there. That is what I don't want. Don't use the java installer,
instead unzip to location in npackd install dir. Thanks

On Fri, Oct 31, 2014 at 1:34 PM, <windows-package-manager@googlecode.com>
wrote:

Original comment by cmtopi...@gmail.com on 9 Nov 2014 at 5:19

GoogleCodeExporter commented 9 years ago 
many programs that use Java depend on the current behavior. I will not change 
this package.

Original comment by tim.lebe...@gmail.com on 3 Jan 2015 at 12:14

GoogleCodeExporter commented 9 years ago 
Java needs to be installed once and then used by other packages that depend
on it.

On Sat, Jan 3, 2015 at 6:14 AM, <windows-package-manager@googlecode.com>
wrote:

Original comment by cmtopi...@gmail.com on 6 Jan 2015 at 9:39

GoogleCodeExporter commented 9 years ago 
Spring Tool Suite is an Eclipse based project. By default it searches for JREs 
using the Windows Registry and the PATH variable. If you install the JDK 
manually, I would recommend to point STS to the JDK via the "vm" parameter as 
described here:

http://stackoverflow.com/questions/4419983/a-jre-or-jdk-must-be-available-in-ord
er-to-run-eclipse-no-jvm-was-found-after-s

Original comment by tim.lebe...@gmail.com on 7 Jan 2015 at 10:14

GoogleCodeExporter commented 9 years ago

Original comment by tim.lebe...@gmail.com on 16 Jan 2015 at 7:13

GoogleCodeExporter commented 9 years ago 
Gotcha.

On Fri, Jan 16, 2015 at 1:13 PM, <windows-package-manager@googlecode.com>
wrote:

Original comment by cmtopi...@gmail.com on 16 Jan 2015 at 8:00