You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2015/08/20 00:49:45 UTC

[jira] [Created] (MPOM-80) publish to /components instead of /content

Hervé Boutemy created MPOM-80:
---------------------------------

             Summary: publish to /components instead of /content
                 Key: MPOM-80
                 URL: https://issues.apache.org/jira/browse/MPOM-80
             Project: Maven POMs
          Issue Type: Task
          Components: maven
    Affects Versions: MAVEN-26
            Reporter: Hervé Boutemy
            Assignee: Hervé Boutemy
             Fix For: MAVEN-27


Maven use of CMS's extpaths.txt (with hundreds of entries) made the CMS publication from staging to production really slow

a new better strategy has been found to mix site content with components documentation, now based on publishing these 2 parts in 2 different locations and create .htaccess rewrite rule to mix the 2

this was:
- explaned on maven-dev ML in http://mail-archives.apache.org/mod_mbox/maven-dev/201503.mbox/%3C1757469.VDPVErWv7t%40herve-desktop%3E
- done in [r1669973|http://svn.apache.org/r1669973]
- documented in [r1670224|http://svn.apache.org/r1670224]

the change has to be done in Maven parent POM, then it will be used by every Maven component when upgrading parent



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)