Spring/spring-batch-extensions
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

URL Cleanup

Browse Source 
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# HTTP URLs that Could Not Be Fixed
These URLs were unable to be fixed. Please review them to see if they can be manually resolved.

* [ ] http://jexcelapi.sourceforge.net (200) with 1 occurrences could not be migrated:
   ([https](https://jexcelapi.sourceforge.net) result AnnotatedConnectException).

# Fixed URLs

## Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

* [ ] http://progit.org/book/ch3-6.html (301) with 4 occurrences migrated to:
  https://progit.org/book/ch3-6.html ([https](https://progit.org/book/ch3-6.html) result SSLHandshakeException).
* [ ] http://progit.org/book/ch5-2.html (301) with 2 occurrences migrated to:
  https://progit.org/book/ch5-2.html ([https](https://progit.org/book/ch5-2.html) result SSLHandshakeException).
* [ ] http://book.git-scm.com/4_interactive_rebasing.html (301) with 1 occurrences migrated to:
  https://book.git-scm.com/4_interactive_rebasing.html ([https](https://book.git-scm.com/4_interactive_rebasing.html) result 404).
* [ ] http://help.github.com/send-pull-requests (404) with 2 occurrences migrated to:
  https://help.github.com/send-pull-requests ([https](https://help.github.com/send-pull-requests) result 404).

## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* [ ] http://maven.apache.org with 1 occurrences migrated to:
  https://maven.apache.org ([https](https://maven.apache.org) result 200).
* [ ] http://poi.apache.org with 1 occurrences migrated to:
  https://poi.apache.org ([https](https://poi.apache.org) result 200).
* [ ] http://projects.spring.io/spring-batch/ with 1 occurrences migrated to:
  https://projects.spring.io/spring-batch/ ([https](https://projects.spring.io/spring-batch/) result 200).
* [ ] http://spring.io/tools/sts with 1 occurrences migrated to:
  https://spring.io/tools/sts ([https](https://spring.io/tools/sts) result 200).
* [ ] http://stackoverflow.com/faq with 1 occurrences migrated to:
  https://stackoverflow.com/faq ([https](https://stackoverflow.com/faq) result 200).
* [ ] http://stackoverflow.com/questions/134882/undoing-a-git-rebase with 1 occurrences migrated to:
  https://stackoverflow.com/questions/134882/undoing-a-git-rebase ([https](https://stackoverflow.com/questions/134882/undoing-a-git-rebase) result 200).
* [ ] http://stackoverflow.com/questions/tagged/spring-batch with 1 occurrences migrated to:
  https://stackoverflow.com/questions/tagged/spring-batch ([https](https://stackoverflow.com/questions/tagged/spring-batch) result 200).
* [ ] http://docs.spring.io/spring-batch/reference/html/configureJob.html with 1 occurrences migrated to:
  https://docs.spring.io/spring-batch/reference/html/configureJob.html ([https](https://docs.spring.io/spring-batch/reference/html/configureJob.html) result 301).
* [ ] http://help.github.com/fork-a-repo/ with 2 occurrences migrated to:
  https://help.github.com/fork-a-repo/ ([https](https://help.github.com/fork-a-repo/) result 301).
* [ ] http://help.github.com/send-pull-requests/ with 2 occurrences migrated to:
  https://help.github.com/send-pull-requests/ ([https](https://help.github.com/send-pull-requests/) result 301).
* [ ] http://help.github.com/set-up-git-redirect with 1 occurrences migrated to:
  https://help.github.com/set-up-git-redirect ([https](https://help.github.com/set-up-git-redirect) result 301).
This commit is contained in:
Spring Operator
2019-03-20 17:05:17 -05:00
committed by Mahmoud Ben Hassine
parent 6728f46574
commit b4a903976c
3 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
CONTRIBUTING.md
View File

@@ -30,7 +30,7 @@ Once you've completed the web form, simply add the following in a comment on you
1. Go to [https://github.com/spring-projects/spring-batch-extensions](https://github.com/spring-projects/spring-batch-extensions)
2. Hit the "fork" button and choose your own github account as the target
3. For more details see [http://help.github.com/fork-a-repo/](http://help.github.com/fork-a-repo/)
3. For more details see [https://help.github.com/fork-a-repo/](https://help.github.com/fork-a-repo/)
## Setup your Local Development Environment
@@ -50,14 +50,14 @@ _you should see branches on origin as well as upstream, including 'master'_
* _Always_ work on topic branches (Typically an issue ID or descriptive identifier as the branch name).
- For example, to create and switch to a new branch for issue BATCHEXT-123: `git checkout -b BATCHEXT-123`
* You might be working on several different topic branches at any given time, but when at a stopping point for one of those branches, commit (a local operation).
* Please follow the "Commit Guidelines" described in this chapter of Pro Git: [http://progit.org/book/ch5-2.html](http://progit.org/book/ch5-2.html)
* Please follow the "Commit Guidelines" described in this chapter of Pro Git: [https://progit.org/book/ch5-2.html](https://progit.org/book/ch5-2.html)
* Then to begin working on another issue (say BATCHEXT-101): `git checkout BATCHEXT-101`. The _-b_ flag is not needed if that branch already exists in your local repository.
* When ready to resolve an issue or to collaborate with others, you can push your branch to origin (your fork), e.g.: `git push origin BATCHEXT-123`
* If you want to collaborate with another contributor, have them fork your repository (add it as a remote) and `git fetch <your-username>` to grab your branch. Alternatively, they can use `git fetch --all` to sync their local state with all of their remotes.
* If you grant that collaborator push access to your repository, they can even apply their changes to your branch.
* When ready for your contribution to be reviewed for potential inclusion in the master branch of the canonical *spring-batch-extensions* repository (what you know as 'upstream'), issue a pull request to the *spring-batch-extensions* repository (for more detail, see [http://help.github.com/send-pull-requests/](http://help.github.com/send-pull-requests/)).
* When ready for your contribution to be reviewed for potential inclusion in the master branch of the canonical *spring-batch-extensions* repository (what you know as 'upstream'), issue a pull request to the *spring-batch-extensions* repository (for more detail, see [https://help.github.com/send-pull-requests/](https://help.github.com/send-pull-requests/)).
* The project lead may merge your changes into the upstream master branch as-is, he may keep the pull request open yet add a comment about something that should be modified, or he might reject the pull request by closing it.
* A prerequisite for any pull request is that it will be cleanly merge-able with the upstream master's current state. **This is the responsibility of any contributor.** If your pull request cannot be applied cleanly, the project lead will most likely add a comment requesting that you make it merge-able. For a full explanation, see the Pro Git section on rebasing: [http://progit.org/book/ch3-6.html](http://progit.org/book/ch3-6.html). As stated there: "> Often, you’ll do this to make sure your commits apply cleanly on a remote branch — perhaps in a project to which you’re trying to contribute but that you don’t maintain."
* A prerequisite for any pull request is that it will be cleanly merge-able with the upstream master's current state. **This is the responsibility of any contributor.** If your pull request cannot be applied cleanly, the project lead will most likely add a comment requesting that you make it merge-able. For a full explanation, see the Pro Git section on rebasing: [https://progit.org/book/ch3-6.html](https://progit.org/book/ch3-6.html). As stated there: "> Often, you’ll do this to make sure your commits apply cleanly on a remote branch — perhaps in a project to which you’re trying to contribute but that you don’t maintain."
## Keeping your Local Code in Sync
* As mentioned above, you should always work on topic branches (since 'master' is a moving target). However, you do want to always keep your own 'origin' master branch in synch with the 'upstream' master.
@@ -70,8 +70,8 @@ _you should see branches on origin as well as upstream, including 'master'_
- Then: `git pull upstream master`
- Switch back to the topic branch: `git checkout BATCHEXT-123` (no -b needed since the branch already exists)
- Rebase the topic branch to minimize the distance between it and your recently synched master branch: `git rebase master`
(Again, for more detail see the Pro Git section on rebasing: [http://progit.org/book/ch3-6.html](http://progit.org/book/ch3-6.html))
* **Note** You cannot rebase if you have already pushed your branch to your remote because you'd be rewriting history (see **'The Perils of Rebasing'** in the article). If you rebase by mistake, you can undo it as discussed [in this stackoverflow discussion](http://stackoverflow.com/questions/134882/undoing-a-git-rebase). Once you have published your branch, you need to merge in the master rather than rebasing.
(Again, for more detail see the Pro Git section on rebasing: [https://progit.org/book/ch3-6.html](https://progit.org/book/ch3-6.html))
* **Note** You cannot rebase if you have already pushed your branch to your remote because you'd be rewriting history (see **'The Perils of Rebasing'** in the article). If you rebase by mistake, you can undo it as discussed [in this stackoverflow discussion](https://stackoverflow.com/questions/134882/undoing-a-git-rebase). Once you have published your branch, you need to merge in the master rather than rebasing.
* Now, if you issue a pull request, it is much more likely to be merged without conflicts. Most likely, any pull request that would produce conflicts will be deferred until the issuer of that pull request makes these adjustments.
* Assuming your pull request is merged into the 'upstream' master, you will actually end up pulling that change into your own master eventually, and at that time, you may decide to delete the topic branch from your local repository and your fork (origin) if you pushed it there.
- to delete the local branch: `git branch -d BATCHEXT-123`
@@ -172,7 +172,7 @@ Search the codebase to find related unit tests and add additional @Test methods
## Squash commits
Use `git rebase --interactive`, `git add --patch` and other tools to "squash" multiple commits into atomic changes. In addition to the man pages for git, there are many resources online to help you understand how these tools work. Here is one: http://book.git-scm.com/4_interactive_rebasing.html.
Use `git rebase --interactive`, `git add --patch` and other tools to "squash" multiple commits into atomic changes. In addition to the man pages for git, there are many resources online to help you understand how these tools work. Here is one: https://book.git-scm.com/4_interactive_rebasing.html.
## Use your real name in git commits
@@ -205,6 +205,6 @@ Make sure that all tests pass prior to submitting your pull request.
Add a comment to the associated [GitHub Issue Tracker][] issue(s) linking to your new pull request.
[help documentation]: http://help.github.com/send-pull-requests
[help documentation]: https://help.github.com/send-pull-requests
[GitHub Issue Tracker]: https://github.com/spring-projects/spring-batch-extensions/issues

14
README.md
View File

@@ -91,19 +91,19 @@ The Spring Batch Extensions Framework is released under version 2.0 of the [Apac
**We look forward to your contributions!!**
[Spring Batch]: https://github.com/spring-projects/spring-batch
[Spring Batch Project]: http://projects.spring.io/spring-batch/
[Spring Batch Project]: https://projects.spring.io/spring-batch/
[Spring organization]: https://github.com/spring-projects
[spring-batch tag]: http://stackoverflow.com/questions/tagged/spring-batch
[Stack Overflow]: http://stackoverflow.com/faq
[spring-batch tag]: https://stackoverflow.com/questions/tagged/spring-batch
[Stack Overflow]: https://stackoverflow.com/faq
[Commercial support]: https://www.vmware.com/support/services/vfabric-developer.html
[GitHub Issue Tracker]: https://github.com/spring-projects/spring-batch-extensions/issues
[Git]: http://help.github.com/set-up-git-redirect
[Pull requests]: http://help.github.com/send-pull-requests
[Git]: https://help.github.com/set-up-git-redirect
[Pull requests]: https://help.github.com/send-pull-requests
[Spring Batch Admin]: https://github.com/spring-projects/spring-batch-admin
[Spring XD]: https://github.com/spring-projects/spring-xd
[Spring for Apache Hadoop]: https://github.com/spring-projects/spring-hadoop
[Spring Boot]: https://github.com/spring-projects/spring-boot
[Spring Tool Suite]: http://spring.io/tools/sts
[Spring Tool Suite]: https://spring.io/tools/sts
[Apache License]: http://www.apache.org/licenses/LICENSE-2.0
[Maven]: http://maven.apache.org
[Maven]: https://maven.apache.org
[Contributor Guidelines]: com/spring-projects/spring-batch-extensions/blob/master/CONTRIBUTING.md

4
spring-batch-excel/README.md
View File

@@ -4,7 +4,7 @@ Spring Batch extension which contains `ItemReader` implementations for Excel. Su
## Configuration
Next to the [configuration of Spring Batch](http://docs.spring.io/spring-batch/reference/html/configureJob.html) one needs to configure the `ItemReader` for the desired framework.
Next to the [configuration of Spring Batch](https://docs.spring.io/spring-batch/reference/html/configureJob.html) one needs to configure the `ItemReader` for the desired framework.
There are 2 `ItemReaders` one can configure:
- `org.springframework.batch.item.excel.jxl.JxlItemReader`
@@ -74,4 +74,4 @@ Uses a `BeanWrapper` to convert a given row into an object. Uses the column name
</bean>
[1]: http://jexcelapi.sourceforge.net
[2]: http://poi.apache.org
[2]: https://poi.apache.org