jdk，maven，PHPstudy的安装与配置

步骤1、安装JDK选择安装目录，安装过程中会出现两次安装提示。第一次是安装jdk，第二次是安装 jre。建议两个都安装在同一个java文件夹中的不同文件夹中。(不能都安装在java文件夹的根目录下，jdk和jre安装在同一文件夹会出错)。

 

步骤2、(1)安装jdk随意选择目录 只需把默认安装目录\java之前的目录修改即可。

　　(2)安装jre→更改→\java之前目录和安装 jdk目录相同即可。

　　注：若无安装目录要求，可全默认设置。无需做任何修改，两次均直接点下一步。

 

 

步骤3、安装完JDK后配置环境变量计算机→属性→高级系统设置→高级→环境变量。

步骤4、系统变量→新建JAVA_HOME变量 。

　　变量值填写jdk的安装目录(本人是E:\Java\jdk1.7.0)。

步骤5、系统变量→寻找Path变量→编辑。

　　在变量值最后输入%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;(注意原来Path的变量值末尾有没有;号，如果没有，先输入;号再输入上面的代码)。

 

步骤6、系统变量→新建CLASSPATH变量。

　　变量值填写.;%JAVA_HOME%\lib;%JAVA_HOME%\lib\tools.jar(注意最前面有一点)。系统变量配置完毕。

 

 

步骤7、检验是否配置成功运行cmd输入java-version(java和-version之间有空格)。

　　若如图所示 显示版本信息则说明安装和配置成功。

Maven的安装与配置 

无视下载速度以及需要其他版本的伙伴点此进入Maven官网下载

选择左侧Download
点击箭头所指的链接进行下载
下载完成后，选择一个路径进行解压

然后配置path环境变量,

系统变量:MAVEN_HOME = F:\dev\apache-maven-3.6.1
系统变量:path = %MAVEN_HOME%\bin

二、配置settings文件
在F:\dev\apache-maven-3.6.1\conf下可以找到settings文件，打开(嫌麻烦的直接看最后一步)

找到第52行，这里是maven默认的仓库

我们复制第53行

<localRepository>/path/to/local/repo</localRepository>
1
将它拿到注释外并将中间的内容改成你需要的路径，如图

<localRepository>F:/repository</localRepository>
1
这里的路径随便设置，注意这里是正斜杠

因为国外的服务器下载jar包很慢所以我们改为阿里云服务器（大约在150行左右），这两个仓库只用选一个(根据大家反馈建议使用第一个，第二个在有的版本可能会出现warning)
 <!-- 阿里云仓库 -->
        <mirror>
            <id>alimaven</id>
            <mirrorOf>central</mirrorOf>
            <name>aliyun maven</name>
            <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
        </mirror>
     或者
      <mirror>
        <id>nexus-aliyun</id>
        <mirrorOf>*</mirrorOf>
        <name>Nexus aliyun</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public</url>
     </mirror>
如图，要夹在两个mirrors标签之间
在最后配置jdk，也要夹在两个profiles标签之间(我这里使用的为jdk8)

<!-- java版本 --> 
<profile>
      <id>jdk-1.8</id>
      <activation>
        <activeByDefault>true</activeByDefault>
        <jdk>1.8</jdk>
      </activation>

      <properties>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
        <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
      </properties>
</profile>

配置完成，在命令行输入mvn help:system测试，看到下载链接里面是ailiyun的链接表示配置成功

嫌麻烦的直接复制配置文件的内容即可,不过路径还是要改(参考第3步)

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->
<localRepository>F:/repository</localRepository>
  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  
    <!-- mirror
    <mirrors>
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     </mirrors>
     -->
     <!-- 阿里云仓库 -->
 <mirrors>
     <mirror>
            <id>nexus-aliyun</id>
            <mirrorOf>*</mirrorOf>
            <name>Nexus aliyun</name>
            <url>http://maven.aliyun.com/nexus/content/groups/public</url>
    </mirror>
</mirrors>
  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
    <!-- profile
    <profiles>
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
      
    -->
<profiles>
<profile>
      <id>jdk-1.8</id>
      <activation>
        <activeByDefault>true</activeByDefault>
        <jdk>1.8</jdk>
      </activation>

      <properties>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
        <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
      </properties>
</profile>
</profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

HPHstudy的安装与配置

目前，PHP依然是很多网站建设的首选语言，仅WordPress就占据了全世界所有网站的43%。所以在建站过程中，无论是自行开发还是外包给第三方，在本地搭建一个PHP运行环境都是必不可少的。PhpStudy作为PHP运行环境的集成部署软件，简单方便、快捷好用。所以，这次就来分享一下V8.1版本的安装过程和一些基本配置。

一、下载解压
首先，在搜索引擎的搜索框输入【PhpStudy Windows】进行搜索，然后点击【Windows版phpstudy下载 - 小皮面板(phpstudy)】即可进入下载页面。需要注意的是，不要搜索PhpStudy，如果这样搜索，找到就是Linux版本的页面了。

 

进入官网下载页面以后，就可以下载了。不过，截至笔者发文时，官网的下载界面还是有些错位，非常影响视觉效果。在这里，麻烦宋小宝帮忙喊句话：海燕呐，你可长点心吧！不过还好，下载功能还是正常的。文件大小约为77.71MB。将下载下来的压缩包解压。推荐使用7-Zip，免费开源，清爽干净，超级好用。

 

二、执行安装
在解压的文件夹里，选择名为【phpstudy_x64_8.1.1.3.exe】的文件双击打开，或右键选择【以管理员身份运行】，开始安装。注意，在弹出的第一个安装界面中，一定要点击【自定义选项】查看一下默认的安装目录，如果是C盘以外的分区没有问题。

 

如果想在C盘安装，请尽量安装在本用户的目录下，以避免权限不足的问题。

 

选择安装目录之后，就可以点击【立即安装】了，很快就会安装完成。然后点击桌面生成的快捷图标就可以运行PhpStudy。

三、基本配置
运行PhpStudy以后，可以看到V8.1版本的界面已经做得非常漂亮了，这里要给开发者们点个大大的赞！这时，系统运行的只是PhpStudy软件本身，其实Nginx、Apache、MySQL、PHP等环境并没有运行起来，需要按需启动。一般情况下，我们用得最多的就是Nginx+MySQL+PHP的组合，这种配置也是在生产环境用得最多的，所以强烈推荐。另外，软件默认的开启自启一般不需要打开，否则会影响开机速度，建议关闭。所以，我们需要将【一键启动】下面的【WNMP】选项【启动】，并将【开机启动】选项【停用】。

 

最后需要提醒大家的就是，PhpStudy默认的网站目录是WWW，小伙伴们可以根据需要修改、添加或删除。当然，PhpStudy还有很多其他选项，大家可以根据自己的需要进行个性化设置，基本上都是比较简单的，这里就不再一一赘述。