同步操作将从 Gitee 极速下载/DataCleaner 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
Before anything else, thank you. We are honored that you're even considering contributing to DataCleaner.
This guide will help you get started with DataCleaner's development environment. You'll also find the set of rules you're expected to follow in order to submit improvements and fixes.
Our issue list is avialable on GitHub: DataCleaner issues. It's non-exhaustive and anyone is invited to post their own wishes and requirements as issues.
We use the issue tracker as the primary tool for discussing features. Otherwise it is requested you post a detailed comment for questions on possible issues. Be as descriptive as possible to allow reproducing your experience.
Fork and clone the repository:
> git clone https://github.com/datacleaner/DataCleaner.git DataCleaner
Try your first build:
> cd DataCleaner
> mvn clean install
Please use our issue list to report issues and ideas that you might work on. This is a great way to bounce ideas and get input to your contributions.
When submitting your patch, keep in mind that it should be easy for others to review. Therefore consider:
Your patches receive extra points if there's a good set of unittests with it. If you're contributing a core utility/service/function then it is a requirement.
That said, especially the UI aspects (Swing or web frontend) are generally accepted as "not always feasible to test".
By default the build will include all self-contained tests, including some quick integration tests.
If you plan on submitting code, read this carefully. Please note it is not yet complete.
Our code style looks a lot like any other Java coding guidelines. Distinctive choices though:
A few general rules of thumb:
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。