maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bindul Bhowmik (JIRA)" <>
Subject [jira] [Commented] (MNGSITE-277) Plugin testing documentation links update
Date Tue, 08 Mar 2016 07:47:40 GMT


Bindul Bhowmik commented on MNGSITE-277:

I did visit the source repository page you mentioned. I guess I did not look hard enough,
apologize for that. Looking at that page again, I think I gave up after _A variety of other
subsystems (including obsolete trees replaced by git)_.

My two cents: If you see on that page, most everything like components, plugins is in tables.
While the site repository almost kind of merges into the boilerplate links (anonymous access,
developer access, access behind firewalls, etc.). Maybe one idea could be to move the site
repository into a row in the table with plugins and shared components.

Another page I may not have spent much time on is
I may have gotten the impression that CMS was the way to edit the main site.

Again thanks for your help fixing the docs, and apologize if I caused any inconvenience.

> Plugin testing documentation links update
> -----------------------------------------
>                 Key: MNGSITE-277
>                 URL:
>             Project: Maven Project Web Site
>          Issue Type: Bug
>            Reporter: Anders Hammar
>            Priority: Minor
>         Attachments: MNGSITE-277-plugin-int-test-site.patch
> Reported on the dev mailing list:
> {quote}
> I ran across a few links on the documentation which should probably be
> updated. The pages either use CMS or Confluence, so I am unable to
> send a patch (or know how to).
> On the 'Developers centre - Testing Plugins Strategies' page \[1] on
> the Maven website, under the 'maven-verifier' subsection, the page
> links to the MAVENOLD confluence space for the 'Creating a Maven
> Integration Test' link \[2]; but that should probably point to the same
> page in the MAVEN space \[3].
> On the MAVEN/Creating+a+Maven+Integration+Test \[3] page itself, there
> are several links which point to the SVN location for the Core ITs
> \[4], which should point to the new Git location \[5] if I am not
> mistaken. Also the archetype catalog used in that page \[6] is no
> longer available (links to a Codehaus page), and probably also needs
> to point somewhere else.
> Regards,
> Bindul
> \[1]
> \[2]
> \[3]
> \[4]
> \[5]
> \[6]
> {quote}

This message was sent by Atlassian JIRA

View raw message