Android studio 解决Gradle下载缓慢的问题 一、前言第一次创建项目时AS会直接从默认的仓库下载，由于是国外服务器，下载非常慢，有时部分库还无法下载。所以我们需要将默认的仓库地址替换为国内的阿里云镜像地址，从而提升下载速度。二、步骤步骤一：　　打开【build.gradle】文件。步骤二：　　将repositories标签中的内容替换成自己需要的阿里镜像maven仓库地址。　　阿里镜像maven仓库地址对应表请查看附录。repositories { maven { url 'https://maven.aliyun.com/repository/central' } maven { url 'https://maven.aliyun.com/repository/google' } maven { url 'https://maven.aliyun.com/repository/gradle-plugin' } maven { url 'https://maven.aliyun.com/repository/jcenter' } maven { url 'https://maven.aliyun.com/repository/public' } maven { url 'https://jitpack.io' } }三、附录仓库名称阿里云仓库地址源地址centralhttps://maven.aliyun.com/repository/centralhttps://repo1.maven.org/maven2/jcenterhttps://maven.aliyun.com/repository/jcenterhttp://jcenter.bintray.com/publichttps://maven.aliyun.com/repository/publiccentral仓和jcenter仓的聚合仓googlehttps://maven.aliyun.com/repository/googlehttps://maven.google.com/gradle-pluginfhttps://maven.aliyun.com/repository/gradle-pluginhttps://plugins.gradle.org/m2/springhttps://maven.aliyun.com/repository/springhttp://repo.spring.io/libs-milestone/spring-pluginhttps://maven.aliyun.com/repository/spring-pluginhttp://repo.spring.io/plugins-release/grails-corehttps://maven.aliyun.com/repository/grails-corehttps://repo.grails.org/grails/coreapache snapshotshttps://maven.aliyun.com/repository/apache-snapshotshttps://repository.apache.org/snapshots/

ktolin的android项目编译突然报错w: Runtime JAR files in the classpath should have the same version. These file 编译报错w: Runtime JAR files in the classpath should have the same version. These files were found in the classpath: e: D:/software/Gradle_workplace/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.5.10/6b84d926e28493be69daf673e40076f89492ef7/kotlin-stdlib-common-1.5.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.13.将这个依赖;implementation “androidx.core:core-ktx:+”去掉就可以编译了；感觉就是冲突了；而且这种androidx开头的感觉有些时候容易有冲突问题，毕竟是新包名依赖感觉不稳定，以后有问题就往这个方向靠就行了；知道问题的大佬也可以指点一下；环境：kotlin版本是1.3.11的；jdk是1.8的；gradle是4.6的；android studio是4.1.3的

破解Gitlab EE 一、docker安装gitlab-ee1.执行安装脚本docker run -d --name gitlabee \ --restart always \ --privileged \ -e GITLAB_SKIP_UNMIGRATED_DATA_CHECK=true \ -p 40001:40001 \ -p 40002:40002 \ -p 40003:40003 \ -v /home/$USER/dockerfile/gitlabee/data/etc:/etc/gitlab \ -v /home/$USER/dockerfile/gitlabee/data/logs:/var/log/gitlab \ -v /home/$USER/dockerfile/gitlabee/data/data:/var/opt/gitlab \ gitlab/gitlab-ee:15.7.0-ee.02.获取root用户登录密码docker exec gitlabee grep 'Password:' /etc/gitlab/initial_root_password得到root用户密码：Password: dwFJvE5IctiBAYiG8jzA0COgEqdu/KDxg8HmSl73rX8=二、修改配置修改 /etc/gitlab.rb 配置文件即可，以下为快速修改脚本命令。记得将IP地址192.168.0.100修改为自己服务器的实际IP本攻略以 192.168.0.100 为例1.修改http访问地址sudo sed -i "s|# external_url 'GENERATED_EXTERNAL_URL'|external_url 'http://192.168.0.100:40002'|g" /home/$USER/dockerfile/gitlabee/data/etc/gitlab.rb2.修改ssh请求地址sudo sed -i "s|# gitlab_rails\['gitlab_ssh_host'\] = 'ssh.host_example.com'|gitlab_rails\['gitlab_ssh_host'\] = '192.168.0.100:40001'|g" /home/$USER/dockerfile/gitlabee/data/etc/gitlab.rb3.重载配置docker exec gitlabee gitlab-ctl reconfigure三、破解gitlab-ee1.使用docker运行rubydocker run -it --rm ruby /bin/bash或者本地安装ruby,需要2.3或以上sudo apt-get install ruby2.使用ruby生成许可证gem install gitlab-license注： docker容器内执行该命令后不会自动结束并换行，按 Ctrl+C 结束3.创建证书文件1.创建license.rb文件，并输入脚本内容cat > license.rb注： 修改脚本中的开始和结束时间require "openssl" require "gitlab/license" key_pair = OpenSSL::PKey::RSA.generate(2048) File.open("license_key", "w") { |f| f.write(key_pair.to_pem) } public_key = key_pair.public_key File.open("license_key.pub", "w") { |f| f.write(public_key.to_pem) } private_key = OpenSSL::PKey::RSA.new File.read("license_key") Gitlab::License.encryption_key = private_key license = Gitlab::License.new license.licensee = { "Name" => "Your Company", "Company" => "Your Company", "Email" => "example@test.com", } license.starts_at = Date.new(2023, 1, 1) # 开始时间 license.expires_at = Date.new(2053, 1, 1) # 结束时间 license.notify_admins_at = Date.new(2052, 12, 1) license.notify_users_at = Date.new(2052, 12, 1) license.block_changes_at = Date.new(2053, 1, 1) license.restrictions = { active_user_count: 10000, } puts "License:" puts license data = license.export puts "Exported license:" puts data File.open("GitLabBV.gitlab-license", "w") { |f| f.write(data) } public_key = OpenSSL::PKey::RSA.new File.read("license_key.pub") Gitlab::License.encryption_key = public_key data = File.read("GitLabBV.gitlab-license") $license = Gitlab::License.import(data) puts "Imported license:" puts $license unless $license raise "The license is invalid." end if $license.restricted?(:active_user_count) active_user_count = 10000 if active_user_count > $license.restrictions[:active_user_count] raise "The active user count exceeds the allowed amount!" end end if $license.notify_admins? puts "The license is due to expire on #{$license.expires_at}." end if $license.notify_users? puts "The license is due to expire on #{$license.expires_at}." end module Gitlab class GitAccess def check(cmd, changes = nil) if $license.block_changes? return build_status_object(false, "License expired") end end end end puts "This instance of GitLab Enterprise Edition is licensed to:" $license.licensee.each do |key, value| puts "#{key}: #{value}" end if $license.expired? puts "The license expired on #{$license.expires_at}" elsif $license.will_expire? puts "The license will expire on #{$license.expires_at}" else puts "The license will never expire." end然后 Ctrl + C 退出输入2.生成许可证和公钥文件ruby license.rb执行命令后会在当前目录下生成 三个文件 GitLabBV.gitlab-license 、 license_key 、 license_key.pub4.使用许可证1.读取公钥和许可证密钥读取公钥：cat license_key.pub得到一串公钥-----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwMq1zZocqfF3M2g4ReXJ UYgQ5QOCeLVGrvUpqfcAU7xCmA6lMOH5XqzuT/5hntMWYtQin26BL1n0nvDV1Mkz obAVNms9bK9KLRHaihLugjOWUh3aiF2vgXU+5Hq1+pXKiePDNNKf/l0xBGsuYBLG c/d+AjqmUJueHJYjtRUQsEpIF3jpjEQFkp5pJCOViGkU3MXbUGtFi5GCyS3WEYEY GMoz+joGiVjIJVA3uPIAZnkNouccHNrNZY6Ryh/KrPqTmBC/brVYbgqsuY7O89Mb 2xBcm84u9rdfm1WnsRQeNGhQTjz5Y8V3XvFiYi6FKl+PCx4Ppw88VCpQynGejB2Q vwIDAQAB -----END PUBLIC KEY-----读取许可证密钥：cat GitLabBV.gitlab-license得到一串密钥eyJkYXRhIjoiR1BESmQ3SzFTTmVXTmRGR3RkMUZRSjY2ajRrdkZPbGIrak14 R1dpRTF0TS9PdTBZSWs5OFRRK2VsenpVXG40bTlmWFB1MXlPdDFCNFc4L2lh ZExRcTVUMDhCeEE2QndIOUMwTHVqSEJuaHhidTVqY0twSHlpUnBUUlhcblBP MVZBYzBJR0RRQWlOTFdXRXE2a0RTaGRLU0F5TllacnFlT3BlNWxKUzBLSXRC Z3NlaW80NklSTUpDVFxudHFnMitpS250d1hTRW5IWnVKVmlPak8xRDh1ODd6 cFVZSU91VDlWNWdFOVRZbnpzM1lpOWxQSlpwU0xyXG5OMVVhRTdaK05NTklI RkNxZEFDWDNGN1ltZ2hjWUdNYU1zMk1iVFdSWkx2STk3QVk4SVNwdGdxalRD Y25cblpnV0I1SllDUHdRSzdRVkVFQ2xRL0IzSnNibzY2Z3hoSjJndkxMakZ1 SWlJWlBDeXg5Qy9hQmg5UmZJa1xuTERZanJQQ21XTDBkYjhFVFFQK0tPMVpp SFhQZzFqaXI2VmJQelhwblIyYnBpczE5MmkrTG5wQ3F0ZXVMXG56UmlIMGpQ OWZqcG5WUjl5SVNpTEI5VEwzSGNETUZMemxmWDQ5cktuLzZzejVYZ0ZWejd4 U3JqQk9KMVdcbnNHanl0bGNMNjVjbTVUZCtrZlRoL1ZESER0ajgvaU9mVkZJ Z000eE1NSUtXczdKb2tkK3V2V2t0WDlUNVxuM0JpWExxNGk2azFRR2JVa0Jj UFFCaGRjRWpPbUo5Sk9UTGJVZ1BMT0ZlcGNna0Z5dC85alpQaFNRR0JCXG43 cDFIdmpyZnQzTzNyenNsU2tqTGdkMjhpYlFNTytUU3ozOGh0cExUd1JTbzVH VVpvWURoWU9tSlNzSlBcbm13PT1cbiIsImtleSI6IklST1p2YTNoRUx1QW8x UkdrVGNoWm1WTmoyR3NUS0xGRkV5ZWp6dS93UnczS1VLRDZ1WjBlS1IzY0NB V1xub2VINHVtOGtGcEJQaGZtc2tqcVg0QWxOTVRNT3pWbE5FeEZrZzFBbFcv Zm5MVytlTHBKakk2NTZDUjNoXG5JWDRKcTBQVUlFeW5ydkQ0RmswQnZmaVBS bVI0Ky9nVS9wY1NwKzR5UllVdDluM0c5aUFzbnFpd3NreGdcbk12ek5zbG02 eEFDbXU5RmIwaWs3OTJCdWlXeFloU2cxdUpyelBXNDd2M2t5M1lGVzU3UXRQ eldyZUp5TFxuSnNRRXc1U3I5YzlFRHh5ZDNXUVdvUnErYWdRckhmNmJla2xt REovQ2trdGQyVU9MNC94VmgwSjF0SHloXG45SlVSRlZQRWFUL3VQWHc1N3ZG eW1hQ2NoeTEvY1grRnJMc29qV2VwcEE9PVxuIiwiaXYiOiJmdTY4WU1neFha LzJJWnRDMU1RTDNBPT1cbiJ92.替换 gitlab-ee 公钥内容docker exec -it gitlabee /bin/shvi /opt/gitlab/embedded/service/gitlab-rails/.license_encryption_key.pubvi打开文本后非编辑状态下，先清空旧文本，再输入上一步公钥内容清空文本命令:%d3.重启gitlab-eedocker exec gitlabee gitlab-ctl restart4.上传许可证，激活订阅先打开浏览器，登录root账户。http://192.168.0.100:40002然后转到许可证上传界面http://192.168.0.100:40002/admin/application_settings/general填入许可证，激活订阅激活成功后四、其他问题从url导入项目提示错误：Url is blocked: Requests to the local network are not allowed摘自： https://www.lizhiqiang.name/archives/2190.html https://www.cnblogs.com/guoapeng/p/16816476.html

修改idea的maven3远程镜像仓库地址settings.xml 1.找到idea安装目录中maven3插件位置以我自己的安装目录为例： D:\Program Files\JetBrains\IntelliJ IDEA 2020.3\plugins\maven\lib\maven3\conf 修改 settings.xml 文件，原文件几乎没有任何配置。2.修改镜像仓库远程地址在 mirrors 标签中加入以下部分，配置私有镜像仓库地址。可以在私有镜像仓库缓存中央仓库jar包，可以加速本地下载jar包速度。<mirror> <id>maven-public</id> <mirrorOf>*</mirrorOf> <name>maven-public</name> <url>http://192.168.2.199:8080/repository/maven-public/</url> <blocked>true</blocked> </mirror>中央仓库<mirror> <id>maven-public</id> <mirrorOf>*</mirrorOf> <name>maven-public</name> <url>https://repo1.maven.org/maven2/</url> <blocked>true</blocked> </mirror>阿里镜像仓库<mirror> <id>public</id> <mirrorOf>*</mirrorOf> <name>aliyun nexus</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> <blocked>true</blocked> </mirror>或<mirror> <id>mirror-aliyun-releases</id> <mirrorOf>*</mirrorOf> <name>aliyun maven mirror</name> <url>https://maven.aliyun.com/repository/public</url> <blocked>true</blocked> </mirror><?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> --> <!-- 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. |--> <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> --> <mirror> <id>maven-public</id> <mirrorOf>*</mirrorOf> <name>maven-public</name> <url>http://192.168.2.199:8080/repository/maven-public/</url> <blocked>true</blocked> </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.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> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> </settings>3.也可以直接在pom.xml修改镜像仓库远程地址<repositories> <repository> <id>maven-public</id> <name>maven-public</name> <url>http://192.168.2.199:8080/repository/maven-public/</url> <releases> <enabled>true</enabled> </releases> </repository> <repository> <id>public</id> <name>aliyun nexus</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>maven-public</id> <name>maven-public</name> <url>http://192.168.2.199:8080/repository/maven-public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>public</id> <name>aliyun nexus</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories>

FC松鼠大战2金手指 金手指代码（需手动输入对应VirtuaNES模拟器）　　03D4-01-05血不减　　00A7-03-000064生命无限　　00A3-01-63花朵无限　　00A9-01-05最高等级　　0344-11-54无敌　　00D8-01-09PASS　　0072-02-0708最终关FC　　00AX-01-64 生命数　　X：7=1P，8=2P　　034X-01-54 透明无敌　　X：4=1P，5=2P　　03DX-01-05 血槽　　X：4=1P，5=2P　　00AX-01-05 最高等级　　X：9=1P，A=2P　　00D2-01-2A 快速蓄力　　0072-01-0X 选关　　X=0～8