mirror of
https://github.com/LingCoder/OnJava8.git
synced 2026-08-23 22:43:28 +08:00
186 lines
9.9 KiB
Markdown
186 lines
9.9 KiB
Markdown
# 第二章 安装Java和本书用例
|
||
|
||
现在,我们来为这次阅读之旅作些准备吧!
|
||
|
||
在开始学习 Java 之前,你必须要先安装好 Java 和本书的源代码示例。因为考虑到可能有“专门的初学者”从本书开始学习编程,所以我会仔细解释计算机命令行 Shell 的这个过程。 如果你已经有此方面的经验了,可以跳过这段安装说明。如果你对此处描述的任何术语或过程仍不清楚,还可以通过 Google 搜索找到答案。具体的问题或困难请试着在 StackOverflow 上提问。或者去 YouTube 看有没有相关的安装说明。
|
||
|
||
|
||
## 编辑器
|
||
|
||
首先你需要安装一个编辑器来创建和修改本书用例里的 Java 代码。有可能你还需要一个编辑器来更改系统配置文件。
|
||
|
||
相比一些重量级的 IDE(Integrated Development Environments,开发集成环境)软件,如Eclipse、NetBeans和IntelliJ IDEA (译者注:做项目强烈推荐IDEA),编辑器是一种基础的运行程序的文本编辑器。如果你已经有了一个 IDE 用着还顺手,那就可以直接用了。为了方便后面的学习和统一下教学环境,我推荐大家使用 Atom 这个编辑器。大家可以在 [atom.io](http://atom.io) 网站下载。
|
||
|
||
Atom 是一个免费开源、易于安装且跨平台(支持 Window、Mac和Linux)的文本编辑器。内置支持 Java 文件。相比 IDE 的厚重,她比较轻量级,是学习本书的理想工具。Atom 包含了许多方便的编辑功能,相信你一定会爱上她!更多关于 Atom 使用的细节问题可以到她们的网站上。
|
||
|
||
还有很多其他的编辑器。有一种亚文化的群体,他们热衷于争论哪个更好用!如果你找到一个你更喜欢的编辑器,换一种使用也没什么难度。重要的是,你要找一个用着舒服的。
|
||
|
||
|
||
## Shell
|
||
|
||
如果你之前没有接触过编程,那么有可能对 Shell(命令行窗口) 不太熟悉。shell 的历史可以追溯到早期的计算时代,当时在计算机上的操作是都通过输入命令进行的,计算机通过回显响应。所有的操作都是基于文本的。
|
||
|
||
尽管和现在的图形用户界面相比,Shell 操作方式很原始。但是同时 shell 也为我们提供了许多有用的功特性。在学习本书的过程中,我们会经常使用到 Shell,包括现在这部分的安装,还有运行 Java 程序。
|
||
|
||
Mac:单击聚光灯(屏幕右上角的放大镜图标),然后键入“terminal”。单击看起来像小电视屏幕的应用程序(您也可以单击“return”)。这就启动了你的用户下的 shell窗口。
|
||
|
||
windows:首先,通过目录打开 windows 资源管理器:
|
||
Windows 7: 单击屏幕左下角的“开始”图标,输入“explorer”后按回车键。
|
||
Windows 8: 按 Windows+Q, 输入 “explorer” 后按回车键。
|
||
Windows 10: 按 Windows+E 。
|
||
当资源管理器运行以后,导航到所需目录,用鼠标双击打开。现在单击“资源管理器”窗口左上角的“文件“选项卡,选择“打开 Window PowerShell”启动 Shell。
|
||
|
||
Linux: 在 home 目录打开 Shell。
|
||
Debian: 按 Alt+F2, 在弹出的对话框中输入“gnome-terminal”
|
||
Ubuntu: 在屏幕中鼠标右击,选择 “打开终端”, 或者按住 Ctrl+Alt+T
|
||
Redhat: 在屏幕中鼠标右击,选择 “打开终端”
|
||
Fedora: 按 Alt+F2,在弹出的对话框中输入“gnome-terminal”
|
||
|
||
目录是 Shell 的基础元素之一。目录用来保存文件和其目录。
|
||
|
||
Think of a directory as a tree
|
||
with branches. If books is a directory on your system and it has two
|
||
other directories as branches, for example math and art, we say you
|
||
have a directory books with two subdirectories math and art. We refer to
|
||
them as books/math and books/art since books is their
|
||
parent directory. Note that Windows uses backslashes rather than
|
||
forward slashes to separate the parts of a directory.
|
||
Basic Shell Operations
|
||
The shell operations I show here are approximately identical across
|
||
operating systems. For the purposes of this book, here are the essential
|
||
operations in a shell:
|
||
Change directory: Use cd followed by the name of the
|
||
directory where you want to move, or cd .. if you want to move
|
||
up a directory. If you want to move to a different directory while
|
||
remembering where you came from, use pushd followed by the
|
||
different directory name. Then, to return to the previous
|
||
directory, just say popd.
|
||
Directory listing: ls (dir in Windows) displays all the files
|
||
and subdirectory names in the current directory. Use the wildcard
|
||
* (asterisk) to narrow your search. For example, if you want to list
|
||
all the files ending in “.java,” you say ls *.java (Windows:
|
||
dir *.java). If you want to list the files starting with “F” and
|
||
ending in “.java,” you say ls F*.java (Windows: dir
|
||
F*.java).
|
||
Create a directory: use the mkdir (“make directory”)
|
||
command (Windows: md), followed by the name of the directory
|
||
you want to create. For example, mkdir books (Windows: md
|
||
books).
|
||
Remove a file: Use rm (“remove”) followed by the name of the
|
||
file you wish to remove (Windows: del). For example, rm
|
||
somefile.java (Windows: del somefile.java).
|
||
Remove a directory: use the rm -r command to remove the
|
||
files in the directory and the directory itself (Windows:
|
||
deltree). For example, rm -r books (Windows: deltree
|
||
books).
|
||
Repeat a command: The “up arrow” on all three operating
|
||
systems moves through previous commands so you can edit and
|
||
repeat them. On Mac/Linux, !! repeats the last command and !n
|
||
repeats the nth command.
|
||
Command history: Use history in Mac/Linux or press the
|
||
F7 key in Windows. This gives you a list of all the commands
|
||
you’ve entered. Mac/Linux provides numbers to refer to when you
|
||
want to repeat a command.
|
||
Unpacking a zip archive: A file name ending with .zip is an
|
||
archive containing other files in a compressed format. Both Linux
|
||
and Mac have command-line unzip utilities, and you can install
|
||
a command-line unzip for Windows via the Internet. However,
|
||
in all three systems the graphical file browser (Windows Explorer,
|
||
the Mac Finder, or Nautilus or equivalent on Linux) will browse to
|
||
the directory containing your zip file. Then right-mouse-click on
|
||
the file and select “Open” on the Mac, “Extract Here” on Linux, or
|
||
“Extract all …” on Windows.
|
||
To learn more about your shell, search Wikipedia for Windows Shell
|
||
or, for Mac/Linux, Bash Shell.
|
||
|
||
## Java安装
|
||
|
||
To compile and run the examples, you must first install the Java
|
||
development kit. In this book we use JDK8 (Java 1.8).
|
||
Windows
|
||
1. Follow the instructions at this link to Install Chocolatey.
|
||
2. At a shell prompt, type: choco install jdk8. This takes
|
||
some time, but when it’s finished Java is installed and the
|
||
necessary environment variables are set.
|
||
Macintosh
|
||
The Mac comes with a much older version of Java that won’t work for
|
||
the examples in this book, so you must first update it to Java 8. You
|
||
will need administration rights to perform these steps.
|
||
1. Follow the instructions at this link to Install HomeBrew. Then at a shell
|
||
prompt, execute brew update to make sure you have the
|
||
latest changes.
|
||
2. At a shell prompt, execute brew cask install java.
|
||
Once HomeBrew and Java are installed, all other activities described
|
||
in this book can be accomplished within a guest account, if that suits
|
||
your needs.
|
||
Linux
|
||
Use the standard package installer with the following shell commands:
|
||
Ubuntu/Debian:
|
||
1. sudo apt-get update
|
||
2. sudo apt-get install default-jdk
|
||
Fedora/Redhat:
|
||
1. su-c "yum install java-1.8.0-openjdk"
|
||
|
||
|
||
|
||
## 校验安装
|
||
|
||
Open a new shell and type:
|
||
java -version
|
||
You should see something like the following (Version numbers and
|
||
actual text will vary):
|
||
java version "1.8.0_112"
|
||
Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
|
||
Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
|
||
If you see a message that the command is not found or not recognized,
|
||
review the installation instructions in this chapter. If you still can’t get
|
||
it to work, check StackOverflow.
|
||
|
||
|
||
## 安装和运行本书用例
|
||
|
||
Once you have Java installed, the process to install and run the book
|
||
examples is the same for all platforms:
|
||
1. Download the book examples from the GitHub Repository.
|
||
2. unzip (as described in Basic Shell Operations) the downloaded file into the
|
||
directory of your choice.
|
||
3. Use the Windows Explorer, the Mac Finder, or Nautilus or
|
||
equivalent on Linux to browse to the directory where you
|
||
unzipped OnJava8-Examples, and open a shell there.
|
||
4. If you’re in the right directory, you should see files named
|
||
gradlew and gradlew.bat in that directory, along with
|
||
numerous other files and directories. The directories correspond
|
||
to the chapters in the book.
|
||
5. At the shell prompt, type gradlew run (Windows) or
|
||
./gradlew run (Mac/Linux).
|
||
The first time you do this, Gradle will install itself and numerous other
|
||
packages, so it will take some time. After everything is installed,
|
||
subsequent builds and runs are faster.
|
||
Note you must be connected to the Internet the first time you run
|
||
gradlew so that Gradle can download the necessary packages.
|
||
Basic Gradle Tasks
|
||
There are a large number of Gradle tasks automatically available with
|
||
this book’s build. Gradle uses an approach called convention over
|
||
configuration which results in the availability of many tasks even if
|
||
you’re only trying to accomplish something very basic. Some of the
|
||
tasks that “came along for the ride” with this book are inappropriate or
|
||
don’t successfully execute. Here is a list of the Gradle tasks you will
|
||
typically use:
|
||
gradlew compileJava: Compiles all the Java files in the
|
||
book that can be compiled (some files don’t compile, to
|
||
demonstrate incorrect language usage).
|
||
gradlew run: First compiles, then executes all the Java files in
|
||
the book that can be executed (some files are library
|
||
components).
|
||
gradlew test: Executes all the unit tests (you’ll learn about
|
||
these in Validating Your Code).
|
||
gradlew chapter: ExampleName: Compiles and runs a specific
|
||
example program. For instance, gradlew
|
||
objects:HelloDate.
|
||
|
||
|
||
|
||
<!-- 分页 -->
|
||
<div style="page-break-after: always;"></div>
|
||
|