# docConvert
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin http://192.168.1.180:8930/yc/docconvert.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](http://192.168.1.180:8930/yc/docconvert/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
没有合适的资源?快使用搜索试试~ 我知道了~
Java Word转PDF服务,实现pdfjs在线预览
共128个文件
prefs:19个
jar:19个
xml:12个
需积分: 2 0 下载量 168 浏览量
2023-11-21
18:54:58
上传
评论 1
收藏 34.68MB ZIP 举报
温馨提示
三种常用的word转换pdf的方式,集成了Apose,OpenOffice ,Jcob 提供了所需jar和示例源码。 本身是个转换web服务,可供其他项目对接,也可把源码文件加入的自己的项目中作为接口进行调用,稍作修改即可
资源推荐
资源详情
资源评论
收起资源包目录
Java Word转PDF服务,实现pdfjs在线预览 (128个子文件)
assumedExternalFilesCache 4B
WordToPdfUtil.class 20KB
DocFmtConvert.class 5KB
ConvertUrlServlet.class 3KB
ConvertServlet.class 3KB
DownloadFileServlet.class 2KB
DeleteFileServlet.class 2KB
WordToPdfUtil$miTM.class 1KB
WordToPdfUtil$1.class 714B
.classpath 3KB
org.eclipse.wst.common.component 492B
org.eclipse.wst.jsdt.ui.superType.container 49B
variablesAndContainers.dat 129B
jacob-1.18-x64.dll 201KB
jacob-1.18-x86.dll 164KB
externalFilesCache 4B
_0.fdt 11B
_0.fdt 11B
_0.fdx 12B
_0.fdx 12B
_0.fnm 15B
_0.fnm 15B
_0.frq 0B
_0.frq 0B
segments.gen 20B
segments.gen 20B
.gitignore 10B
.gitignore 0B
docConvert.iml 3KB
properties.index 151B
version.ini 102B
jave-1.0.3.jar 15.05MB
aspose-words-18.6-jdk16.jar 10.58MB
aspose-cells-18.10.jar 6.72MB
unoil-3.0.1.jar 1.3MB
httpclient-4.5.jar 711KB
xstream-1.3.1.jar 421KB
hessian-4.0.8.jar 415KB
httpcore-4.4.1.jar 315KB
ridl-3.0.1.jar 248KB
commons-io-1.4.jar 106KB
jurt-3.0.1.jar 106KB
juh-3.0.1.jar 54KB
jacob.jar 48KB
slf4j-api-1.7.29.jar 40KB
commons-cli-1.2.jar 40KB
httpmime-4.5.jar 40KB
jodconverter-2.2.2.jar 31KB
slf4j-jdk14-1.5.6.jar 9KB
jodconverter-cli-2.2.2.jar 6KB
WordToPdfUtil.java 24KB
DocFmtConvert.java 5KB
ConvertUrlServlet.java 2KB
DownloadFileServlet.java 2KB
ConvertServlet.java 2KB
DeleteFileServlet.java 1KB
.jsdtscope 522B
index.jsp 539B
index.jsp 539B
.lock 0B
.log 5KB
0.log 0B
.log 0B
.log 0B
org.eclipse.rse.internal.core.RSELocalConnectionInitializer.mark 0B
README.md 6KB
MANIFEST.MF 39B
.name 10B
org.eclipse.wst.jsdt.ui.superType.name 6B
nonChainingJarsCache 4B
_0.nrm 4B
_0.nrm 4B
com.genuitec.eclipse.j2eedt.core.prefs 1009B
org.eclipse.jdt.core.prefs 598B
org.eclipse.jdt.ui.prefs 571B
org.eclipse.ui.workbench.prefs 371B
org.eclipse.mylyn.tasks.ui.prefs 194B
com.genuitec.eclipse.migration.prefs 155B
org.eclipse.rse.core.prefs 138B
org.eclipse.ui.ide.prefs 129B
org.eclipse.rse.ui.prefs 100B
org.eclipse.mylyn.monitor.ui.prefs 97B
org.eclipse.epp.logging.aeri.ui.prefs 74B
org.eclipse.m2e.discovery.prefs 73B
org.eclipse.team.ui.prefs 69B
org.eclipse.mylyn.context.core.prefs 62B
org.eclipse.jst.j2ee.webservice.ui.prefs 58B
org.eclipse.core.resources.prefs 57B
org.eclipse.core.runtime.prefs 52B
org.eclipse.ui.prefs 48B
org.eclipse.core.resources.prefs 42B
.project 1KB
.project 289B
node.properties 2KB
convert.properties 1KB
convert.properties 1KB
node.properties 1KB
node.properties 166B
clean-cache.properties 51B
org.eclipse.core.resources 853B
共 128 条
- 1
- 2
资源评论
shaoairong2000
- 粉丝: 0
- 资源: 3
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功