windows,java后端开发常用软件的下载，使用配置

以下软件尽量从官网下载，流程为：确定版本下载->配置环境变量->修改配置文件->启动

版本选择的话，可参考阿里巴巴和apache官网推荐。

1.idea,jdk,maven,MySQL，tomcat官网下载

maven3.3.9的setting.xml 配置阿里云仓库，jdk1.8，根据需求自己改

<!-- 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.

|-->

<mirrors>

<!-- mirror

| 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节点下的全部内容-->

<mirror>

<id>aliyun-central</id>

<mirrorOf>*</mirrorOf>

<name>aliyun central</name>

<url>https://maven.aliyun.com/repository/central\</url>

</mirror>

<mirror>

<id>aliyun-public</id>

<mirrorOf>*</mirrorOf>

<name>aliyun public</name>

<url>https://maven.aliyun.com/repository/public\</url>

</mirror>

<mirror>

<id>aliyun-spring</id>

<mirrorOf>*</mirrorOf>

<name>aliyun spring</name>

<url>https://maven.aliyun.com/repository/spring\</url>

</mirror>

<mirror>

<id>aliyun-spring-plugin</id>

<mirrorOf>*</mirrorOf>

<name>aliyun spring-plugin</name>

<url>https://maven.aliyun.com/repository/spring-plugin\</url>

</mirror>

<mirror>

<id>aliyun-apache-snapshots</id>

<mirrorOf>*</mirrorOf>

<name>aliyun apache-snapshots</name>

<url>

https://maven.aliyun.com/repository/apache-snapshots

</url>

</mirror>

<mirror>

<id>aliyun-google</id>

<mirrorOf>*</mirrorOf>

<name>aliyun google</name>

<url>https://maven.aliyun.com/repository/google\</url>

</mirror>

<mirror>

<id>aliyun-gradle-plugin</id>

<mirrorOf>*</mirrorOf>

<name>aliyun gradle-plugin</name>

<url>https://maven.aliyun.com/repository/gradle-plugin\</url>

</mirror>

<mirror>

<id>aliyun-jcenter</id>

<mirrorOf>*</mirrorOf>

<name>aliyun jcenter</name>

<url>https://maven.aliyun.com/repository/jcenter\</url>

</mirror>

<mirror>

<id>aliyun-releases</id>

<mirrorOf>*</mirrorOf>

<name>aliyun releases</name>

<url>https://maven.aliyun.com/repository/releases\</url>

</mirror>

<mirror>

<id>aliyun-snapshots</id>

<mirrorOf>*</mirrorOf>

<name>aliyun snapshots</name>

<url>https://maven.aliyun.com/repository/snapshots\</url>

</mirror>

<mirror>

<id>aliyun-grails-core</id>

<mirrorOf>*</mirrorOf>

<name>aliyun grails-core</name>

<url>https://maven.aliyun.com/repository/grails-core\</url>

</mirror>

<mirror>

<id>aliyun-mapr-public</id>

<mirrorOf>*</mirrorOf>

<name>aliyun mapr-public</name>

<url>https://maven.aliyun.com/repository/mapr-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.

|

|-->

<profiles>

<!-- profile

| 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.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>

-->

2.seata

https://gitee.com/rabbitsheep99/seata-server-1.6.1

双击bat启动 C:\seata1.6.1\seata-server-1.6.1-master\seata1.6.1\bin>seata-server.bat

3.jmeter

https://mirrors.aliyun.com/apache/jmeter/README.html?spm=a2c6h.25603864.0.0.1ffb69a5lZcCss寻找最近的镜像地址：https://mirrors.aliyun.com/apache/jmeter/README.html?spm=a2c6h.25603864.0.0.1ffb69a5lZcCss
Index of /commons我最近的镜像地址：Index of /commons

双击bat启动 C:\jmeter\apache-jmeter-5.5\bin>jmeter.bat

4.nginx

Index of nginx-local https://mirrors.huaweicloud.com/nginx/
双击exe启动，配置文件：

user nginx;

worker_processes auto;

error_log /var/log/nginx/error.log notice;

pid /var/run/nginx.pid;

events {

worker_connections 20000;

}

http {

include /etc/nginx/mime.types;

default_type application/octet-stream;

log_format main 'remote_addr - remote_user [time_local\] "request" '

'status body_bytes_sent "$http_referer" '

'"http_user_agent" "http_x_forwarded_for" ';

log_format stream_log 'remote_addr upstream_addr - [time_local\] status $upstream_bytes_sent';

access_log /var/log/nginx/access.log main;

sendfile on;

#tcp_nopush on;

keepalive_timeout 65;

gzip on;

include /etc/nginx/conf.d/*.conf;

}

stream {

log_format stream_log 'remote_addr upstream_addr - [time_local\] status $upstream_bytes_sent';

upstream proxy {

server (ip):(port);

}

server {

listen 8889;

proxy_pass proxy;

access_log /var/log/nginx/proxy.log stream_log;

}

}

5.Redis

https://github.com/ServiceStack/redis-windows

双击启动 C:\redis\redis-server.exe

或者：

cd C:\redis

redis-server.exe redis.windows.conf

6.nacos

GitCode - 全球开发者的开源社区,开源代码托管平台

往期内容【win11 nacos2.2.1下载，启动】

单机启动：

C:\nacos\nacos-2.2.1\distribution\bin>startup.cmd

-m standalone

7.RocketMQ

下载 | RocketMQ

开启：

C:\MQ\rocketmq-all-4.9.5-bin-release\bin>

start mqnamesrv.cmd

start mqbroker.cmd -n 0.0.0.0:9876

测试收发：

cd C:\MQ\rocketmq-all-4.9.5-bin-release\bin

.\tools.cmd org.apache.rocketmq.example.quickstart.Producer

.\tools.cmd org.apache.rocketmq.example.quickstart.Consumer

8.sentinel

https://github.com/alibaba/Sentinel

cd C:\sentinel

-D参数要加单引号

java '-Dserver.port=18080' '-Dcsp.sentinel.dashboard.server=localhost:18080' '-Dproject.name=sentinel-dashboard' -jar sentinel-dashboard-1.8.6.jar