maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Harper (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MNGSITE-300) version order not documented
Date Fri, 10 Feb 2017 16:57:41 GMT

    [ https://issues.apache.org/jira/browse/MNGSITE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861533#comment-15861533
] 

Jon Harper edited comment on MNGSITE-300 at 2/10/17 4:57 PM:
-------------------------------------------------------------

Also, it's my first time writing serious apt documentation, so feel free to change the layout/classes
used.

Also, I just noticed in the current state, the patch needs an extra [] before the final note:
{noformat}
+
+    []
+
+  Note: Contrary to what was stated in [...]
{noformat}


was (Author: jonenst):
Also, it's my first time writing serious apt documentation, so feel free to change the layout/classes
used.

Also, I just noticed in the current state, the patch needs an extra [] before the final note:
{noformat}
+
+    []
+
+  Note: Contrary to what was stated in some design documents, for version order, snapshots
are not treated differently than releases or any other qualifier.
{noformat}

> version order not documented
> ----------------------------
>
>                 Key: MNGSITE-300
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-300
>             Project: Maven Project Web Site
>          Issue Type: Bug
>            Reporter: Jon Harper
>         Attachments: doc-version-order-image.png, doc-version-order.patch
>
>
> Documenting the version order. I don't know how many exemples should go there because
there are tons of counter intuitive version orders. Feel free to discuss.
> Also, this was the most concise way I found to document the existing behavior, but it
could be explained differently.
> Created issue as suggested by hervé boutemy.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message