Silly question
Clive_S
Under Root ie C:\Java
Any reason why it would be better to install under root rather than C:
\Program files???
Which version of Java should I install for developing Web & JavaBean
apps??
Regards
Clive
markspace
> Where is best to install Java, TomCat, etc??
>
> Under Root ie C:\Java
>
> Any reason why it would be better to install under root rather than C:
> \Program files???
All of my stuff (Tomcat, Apache, MySQL, Java, etc.) is installed under
C:\Program Files. The only reason I can think of off the top of my head
to not do this is that the space in "Program Files" sometimes messes up
scripts when they see it in the path.
But generally it works just fine. I'd recommend installing under
Program Files, everything expects it to be there.
>
> Which version of Java should I install for developing Web & JavaBean
> apps??
The latest JDK, 1.6.17 I think. Note that JDK is different from the
regular Java install (JRE), but the JDK includes the JRE, so once you
have the JDK you are good to go.
<http://java.sun.com/javase/downloads/index.jsp>
Lew
>> Where is best to install Java, TomCat [sic], etc [sic]??
One question mark suffices to indicate an interrogative.
>> Under Root ie [sic] C:\Java
>>
>> Any reason why it would be better to install under root rather than C:
>> \Program files???
You usually should avoid installing too many things directly in the root
directory.
markspace wrote:
> All of my stuff (Tomcat, Apache, MySQL, Java, etc.) is installed under
> C:\Program Files. The only reason I can think of off the top of my head
> to not do this is that the space in "Program Files" sometimes messes up
> scripts when they see it in the path.
>
> But generally it works just fine. I'd recommend installing under
> Program Files, everything expects it to be there.
Nothing expects Java to be in Program Files unless that's where the registry
locates it. What programs expect is to find Java either where the registry
says or where the envar JAVA_HOME says.
I never install Java under "C:/Program Files/". The installer lets you pick
any location you like. Install it in a location consistent with your policy
for installing stuff.
On multi-drive-letter Windows systems I usually put the OS and closely related
stuff on C: and user stuff on D:, with D: being more capacious. I put all my
Java stuff, including the likes of Tomcat and Glassfish, on D:, often under
D:/java/. Typically there will then be D:/java/netbeans/,
D:/java/apache-commons/, D:/java/sun/javadb/, and so on.
Clive_S wrote:
>> Which version of Java should I install for developing Web & JavaBean
>> apps??
markspace wrote:
> The latest JDK, 1.6.17 I think.
Java 1.6.0_17, a.k.a. Java 6u17.
> Note that JDK is different from the
> regular Java install (JRE), but the JDK includes the JRE,
> so once you have the JDK you are good to go.
>
> <http://java.sun.com/javase/downloads/index.jsp>
--
Lew
alexandre...@yahoo.fr
wrote:
> markspace <nos...@nowhere.com> writes:
> > Clive_S wrote:
> > > Where is best to install Java, TomCat, etc??
> > > Under Root ie C:\Java
> > > Any reason why it would be better to install under root rather than C:
> > > \Program files???
> > All of my stuff (Tomcat, Apache, MySQL, Java, etc.) is installed under
> > C:\Program Files. The only reason I can think of off the top of my head
> > to not do this is that the space in "Program Files" sometimes messes up
>
> In the work computer, where I have to use ms windows, I have created a
> directory progs, which I always replace the stupid "Program files" with
> whenever any installer asks for installation directory.
This is an excellent advice.
Spaces in filenames/directory names tend to break script
and cause problems when working in multi-OS environments.
We go even further than that: we'got guidelines that specifically
state that spaces and non-ASCII characters are forbidden and we've
got build scripts enforcing this rule.
Lew
>> I NEVER install ANYTHING in ANY directory with spaces in the name.
>> In the work computer, where I have to use ms windows, I have created a
>> directory progs, which I always replace the stupid "Program files" with
>> whenever any installer asks for installation directory.
alexandre...@yahoo.fr wrote:
> This is an excellent advice.
>
> Spaces in filenames/directory names tend to break script
> and cause problems when working in multi-OS environments.
>
> We go even further than that: we'got guidelines that specifically
> state that spaces and non-ASCII characters are forbidden and we've
> got build scripts enforcing this rule.
Wow, you guys sure throw the baby out with the bath water.
All you have to do is enclose the path names in quotes.
I've been working with files and directories that have spaces in their names
for decades. My scripts work just fine on them, including the multi-OS ones.
Don't amputate your arm because you banged your thumb.
--
Lew
Clive_S
Roedy Green
<cliv...@yahoo.co.uk> wrote, quoted or indirectly quoted someone who
said :
>Where is best to install Java, TomCat, etc??
Just for balance, here are some reasons to install in Program Files.
Before I start, I too detest file names with spaces. It complicates
typing the name on the command line and other places, such as regexes.
I thing MS put files there just to show off its new ability to handle
file names with spaces, and to force all programmers to deal with
them. For a directory name you type so often, I'd would have preferred
something short like "pf".
1. FileHippo is a useful utility that scans your Program Files
directories and looks for programs and tells you of any out of date.
http://mindprod.com/jgloss/filehippo.html (It can be configured to
look elsewhere, but scanning the root would be very slow.)
2. When you install software or reinstall software, by default it will
go in C:\Program Files. It often takes a bit of dexterity to push it
somewhere else. If you want your clients to install elsewhere, you
will need to provide them instruction to arm wrestle various
installers.
3. If you invited me or someone else like to do some repair work on
your machine, I would expect to find software installed in X:\Program
Files.
4. Vendors likely only test their software installed in Program Files.
They have inadvertently hard coded that assumption in somewhere, e.g.
an uninstaller or something rarely exercised or bitter complained
about when it breaks.
--
Roedy Green Canadian Mind Products
http://mindprod.com
Finding a bug is a sign you were asleep a the switch when coding. Stop debugging, and go back over your code line by line.
Lew
> Just for balance, here are some reasons to install in Program Files.
>
> Before I start, I too detest file names with spaces. It complicates
> typing the name on the command line and other places, such as regexes.
> I thing MS put files there just to show off its new ability to handle
> file names with spaces, and to force all programmers to deal with
> them. For a directory name you type so often, I'd would have preferred
> something short like "pf".
You can (nearly) always refer to "Program Files" as "PROGRA~1" when you need
to eschew spaces.
--
Lew