Skip to content

Commit 425337b

Browse files
committed
feat: add readme
1 parent fdcb2c6 commit 425337b

File tree

2 files changed

+6
-38
lines changed

2 files changed

+6
-38
lines changed

README.md

Lines changed: 3 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,11 @@
11
# ArouterGradlePlugin
22

3+
通过本插件,可以实现在AGP7.4+的[ARouter](https://github.com/alibaba/ARouter)框架自动注册;使用方法和`com.alibaba:arouter-register` 完全一致即可;
34

45

5-
## The reason for the review rejection
66

7-
> We received your plugin submission for "cn.jailedbird.arouter".
8-
>
9-
> Your plugin was flagged for manual review because of the following issue(s):
10-
>
11-
> Plugin ID prefix 'cn.jailedbird.arouter' does not match the GitHub username 'JailedBird'. Please prove ownership of the "jailedbird.cn" domain by adding a TXT record with value "gradle-verification=21V75CTLKFT7ATKNMM1GS9INUOHN1" to your DNS, or use a plugin ID, which ties to your GitHub user id, for example "io.github.JailedBird.plugin"
12-
>
13-
> Your plugin lacks documentation, making its use by the community quite unlikely. If this is a private plugin, consider publishing it to a private repository.
14-
> Please refer to our documentation on plugin approval guidelines for more information: https://plugins.gradle.org/docs/publish-plugin#approval
7+
在App模块下导入此插件(https://plugins.gradle.org/u/zjc), 可以从plugins.gradle.org找到本插件;
158

16-
Leak document
179

18-
> #### Plugin is lacking public documentation
19-
>
20-
> **One typical situation when this problem arises is when the website or VCS URLs provided during plugin publication point to a broken or inaccessible destination. Another one is when the URLs point to, for example, a public GitHub repository, but there is no documentation there (empty README file) or none of it is in English.**
21-
>
22-
> The problem with the lack of documentation is that it makes the adoption of the plugin by the community very unlikely.
23-
>
24-
> The solution to this problem is to either make the documentation publicly available, or, if your plugin is indeed private, consider publishing it to a private repository.
2510

11+
后续我会支持AGP8.0+,注意目前只是beta版本,可能存在性能问题,正确性经过初步的验证;注意最低AGP7.4, 7.4+尚未尝试(适配非常容易),7.4以下无法使用;

README_EN.md

Lines changed: 3 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,7 @@
11
# ArouterGradlePlugin
22

3+
With this plugin, you can automatically register in the [ARouter](https://github.com/alibaba/ARouter) framework for AGP 7.4+ version. The usage is exactly the same as `com.alibaba:arouter-register`.
34

5+
To import this plugin in the App module, you can find it on [plugins.gradle.org](https://plugins.gradle.org/u/zjc).
46

5-
## The reason for the review rejection
6-
7-
> We received your plugin submission for "cn.jailedbird.arouter".
8-
>
9-
> Your plugin was flagged for manual review because of the following issue(s):
10-
>
11-
> Plugin ID prefix 'cn.jailedbird.arouter' does not match the GitHub username 'JailedBird'. Please prove ownership of the "jailedbird.cn" domain by adding a TXT record with value "gradle-verification=21V75CTLKFT7ATKNMM1GS9INUOHN1" to your DNS, or use a plugin ID, which ties to your GitHub user id, for example "io.github.JailedBird.plugin"
12-
>
13-
> Your plugin lacks documentation, making its use by the community quite unlikely. If this is a private plugin, consider publishing it to a private repository.
14-
> Please refer to our documentation on plugin approval guidelines for more information: https://plugins.gradle.org/docs/publish-plugin#approval
15-
16-
Leak document
17-
18-
> #### Plugin is lacking public documentation
19-
>
20-
> **One typical situation when this problem arises is when the website or VCS URLs provided during plugin publication point to a broken or inaccessible destination. Another one is when the URLs point to, for example, a public GitHub repository, but there is no documentation there (empty README file) or none of it is in English.**
21-
>
22-
> The problem with the lack of documentation is that it makes the adoption of the plugin by the community very unlikely.
23-
>
24-
> The solution to this problem is to either make the documentation publicly available, or, if your plugin is indeed private, consider publishing it to a private repository.
25-
7+
In the future, I will also support AGP 8.0+; however, please note that it is currently in beta version and may have performance issues. The correctness has been preliminarily verified. Please be aware that the minimum requirement is AGP 7.4, and it has not been tested with AGP 7.4+ yet (but adaptation is relatively easy). It is not compatible with AGP versions below 7.4.

0 commit comments

Comments
 (0)