Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mojohaus/versions
Versions Maven Plugin
https://github.com/mojohaus/versions
hacktoberfest java maven maven-plugin mojohaus versions-maven-plugin
Last synced: about 3 hours ago
JSON representation
Versions Maven Plugin
- Host: GitHub
- URL: https://github.com/mojohaus/versions
- Owner: mojohaus
- License: apache-2.0
- Created: 2015-05-15T22:54:30.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2024-09-24T13:29:39.000Z (about 17 hours ago)
- Last Synced: 2024-09-25T00:35:14.745Z (about 6 hours ago)
- Topics: hacktoberfest, java, maven, maven-plugin, mojohaus, versions-maven-plugin
- Language: Java
- Homepage: https://www.mojohaus.org/versions/versions-maven-plugin/
- Size: 15.5 MB
- Stars: 337
- Watchers: 29
- Forks: 269
- Open Issues: 42
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# MojoHaus Versions Maven Plugin
This is the [versions-maven-plugin](http://www.mojohaus.org/versions-maven-plugin/).
[](http://www.apache.org/licenses/)
[](https://search.maven.org/artifact/org.codehaus.mojo/versions-maven-plugin)
[](https://github.com/mojohaus/versions-maven-plugin/actions/workflows/maven.yml?query=branch%3Amaster)
## Maintained versions
Versions Maven Plugin requires Maven 3.6.3+ and JDK 1.8+
However, we maintain the latest Plugin version with the latest Maven.
We execute tests against different operating systems and JDKs
by [GitHub Actions](https://github.com/mojohaus/versions-maven-plugin/actions/workflows/maven.yml?query=branch%3Amaster)
## Contributing
### Creating Issues
If you find a problem please first search current opened and closed issues and pull requests.
It can be that someone already has reported similar.
You can also check current [milestone](https://github.com/mojohaus/versions-maven-plugin/milestones)
in order to see what will be in next release.
Only when you can not find similar issue please create a new one in the
[ticket system](https://github.com/mojohaus/versions-maven-plugin/issues)
and describe what is going wrong or what you expect to happen.
If you have a full working example or a log file this is also helpful.
You should of course describe only a single issue in a single ticket and not
mixing up several things into a single issue.
Please always check your issue with the latest Plugin and tha latest Maven version.
### Creating a Pull Request
Before you start working on more complicated change, new feature
it is good practice to create an issue in
the [ticket system](https://github.com/mojohaus/versions-maven-plugin/issues)
or send an emil to [development list](https://www.mojohaus.org/versions-maven-plugin/mailing-lists.html)
and describe what the problem is or what kind of feature you would like to add.
Wait a few days for feedback from other contributors.
Afterwards you can create an appropriate pull request.
It is required if you want to get a pull request to be integrated into please
squash your commits into a single commit which references the optional issue
in the commit message which looks like this:
```
Fixed #Issue - change subject
a description
```
Please take consider that change subject will be used in release notes
and will be present in git history so should be enough descriptive.
This makes it simpler to merge it and this will also close the
appropriate issue automatically in one go.
This make the life as maintainer a little bit easier.
A pull request has to fulfill only a single ticket and should never
create/add/fix several issues in one, cause otherwise the history is hard to
read and to understand and makes the maintenance of the issues and pull request
hard or to be honest impossible.
## Releasing
* Make sure `gpg-agent` is running.
* Execute `./mvnw -B release:prepare release:perform`
For publishing the site do the following:
```
cd target/checkout
../mvnw site
../mvnw scm-publish:publish-scm
```
for multi module site - we need two executions