  ------
  Introduction
  ------
  Robert Scholte
  ------
  2017-11-05
  ------

~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements.  See the NOTICE file
~~ distributed with this work for additional information
~~ regarding copyright ownership.  The ASF licenses this file
~~ to you under the Apache License, Version 2.0 (the
~~ "License"); you may not use this file except in compliance
~~ with the License.  You may obtain a copy of the License at
~~
~~   http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing,
~~ software distributed under the License is distributed on an
~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html

${project.name}

  The Maven JDeprScan plugin is used to scan class files for uses of deprecated API elements.
    
  NOTE: This is an alpha release which means everything can change until we reach the first
  milestone release.

* Goals Overview

  The JDeprScan Plugin has four goals:

  * {{{./jdeprscan-mojo.html}jdeprscan:jdeprscan}} scans the main sources for deprecated APIs.

  * {{{./test-jdeprscan-mojo.html}jdeprscan:test-jdeprscan}} scans the test sources for deprecated APIs.

  * {{{./list-mojo.html}jdeprscan:list}} Prints the set of deprecated APIs. 
    No scanning is done, so no directory, jar, or class arguments should be provided.

  * {{{./help-mojo.html}jdeprscan:help}} displays help information on maven-jdeprscan-plugin.

  []

* Usage

  General instructions on how to use the JDeprScan Plugin can be found on the {{{./usage.html}usage page}}. Some more
  specific use cases are described in the examples given below.

  In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
  free to contact the {{{./mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
  already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
  the {{{./mail-lists.html}mail archive}}.

  If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our
  {{{./issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
  concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
  entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
  Of course, patches are welcome, too. Contributors can check out the project from our
  {{{./source-repository.html}source repository}} and will find supplementary information in the
  {{{http://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.

* Examples

  To provide you with better understanding on some usages of the Maven JDeprScan Plugin,
  you can take a look into the following examples:

  TODO: Add examples.

  []