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

Posted to issues@camel.apache.org by "David Jencks (Jira)" <ji...@apache.org> on 2020/05/08 23:03:00 UTC

[jira] [Closed] (CAMEL-14771) Consider using the master branch tooling for 2.x and 3.0.x catalog construction

     [ https://issues.apache.org/jira/browse/CAMEL-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed CAMEL-14771.
--------------------------------
      Assignee: David Jencks
    Resolution: Won't Fix

I'm taking a different approach to generating tables in 2.x

> Consider using the master branch tooling for 2.x and 3.0.x catalog construction
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-14771
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14771
>             Project: Camel
>          Issue Type: Improvement
>          Components: website
>    Affects Versions: 3.1.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>            Priority: Major
>             Fix For: 3.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The 3.0.x branch includes the tooling needed to construct the components component index pages, but the 2.x branch does not.  Some slight modification and configuration of the master branch tooling allow it to be used for the 2.x index pages.  The modifications are roughly:
>  * excluding some json files that are not intended for the catalog
>  * changing some parameter names that are shared across mojos but have different meanings, so that they may be configured.
> I don't know if this is a good idea or not.  I only changed the one name that conflicts, but if we decide to do this changing some more would be a good idea.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)