Skip to content

[MJAVADOC-638] upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts#39

Merged
olamy merged 1 commit intomasterfrom
MJAVADOC-638_doxia-site-tools-1.9.2
Feb 28, 2020
Merged

[MJAVADOC-638] upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts#39
olamy merged 1 commit intomasterfrom
MJAVADOC-638_doxia-site-tools-1.9.2

Conversation

@olamy
Copy link
Copy Markdown
Member

@olamy olamy commented Feb 28, 2020

Signed-off-by: olivier lamy olamy@apache.org

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MJAVADOC-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify -Prun-its to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

…on Struts

Signed-off-by: olivier lamy <olamy@apache.org>
@olamy olamy merged commit 37d0ef5 into master Feb 28, 2020
@olamy olamy deleted the MJAVADOC-638_doxia-site-tools-1.9.2 branch February 28, 2020 06:07
@jira-importer
Copy link
Copy Markdown

Resolve #939

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants