Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Apache Maven Site Plugin

License

NotificationsYou must be signed in to change notification settings

apache/maven-site-plugin

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,612 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Apache License, Version 2.0, January 2004Maven CentralMaven CentralReproducible BuildsJenkins StatusJenkins tests

You have found a bug, or you have an idea for a cool new feature? Contributingcode is a great way to give something back to the open source community. Beforeyou dig right into the code, there are a few guidelines that we needcontributors to follow so that we can have a chance of keeping on top ofthings.

Getting Started

  • Make sure you have aGitHub account.
  • If you're planning to implement a new feature, it makes sense to discuss your changeson thedev list first.This way you can make sure you're not wasting your time on something that isn'tconsidered to be in Apache Maven's scope.
  • Submit a ticket for your issue, assuming one does not already exist.
    • Clearly describe the issue, including steps to reproduce when it is a bug.
    • Make sure you fill in the earliest version that you know has the issue.
  • Fork the repository on GitHub.

Making and Submitting Changes

We accept Pull Requests via GitHub. Thedeveloper mailing list is themain channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:

  • Create a topic branch from where you want to base your work (this is usually the master branch).Push your changes to a topic branch in your fork of the repository.
  • Make commits of logical units.
  • Respect the original code style: by using the samecodestyle,patches should only highlight the actual difference, not being disturbed by any formatting issues:
    • Only use spaces for indentation.
    • Create minimal diffs - disable on save actions like reformat source code or organize imports.If you feel the source code should be reformatted, create a separate PR for this change.
    • Check for unnecessary whitespace withgit diff --check before committing.
  • Make sure you have added the necessary tests (JUnit/IT) for your changes.
  • Run all the tests withmvn -Prun-its verify to assure nothing else was accidentally broken.
  • Submit a pull request to the repository in the Apache organization.

If you plan to contribute on a regular basis, please consider filing acontributor license agreement.

Additional Resources


[8]ページ先頭

©2009-2026 Movatter.jp