Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #11676 Components paths in build-manifest should be relative to plugin path
    Actions
    Infos
    #11676
    Joris MASSON (jmasson)
    2018-06-25 15:14
    2018-06-25 12:41
    12018
    Details
    Components paths in build-manifest should be relative to plugin path
    Currently, we are forced to provide the plugin path for webpack "components" in build-manifest.json
    It is the only path behaving that way and forces everyone to name their plugin folder the same.
    It should behave like all other paths and be relative from the plugin base dir.
    Other
    All
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Empty
    Closed
    2018-06-25
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #11517 Tuleap Releases 10.3 Delivered 2018-07-19 18:00 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #11676

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/90/11790/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 18f0b72122
    User avatar Marie Ange Garnier (marieange) , 2018-06-25 14:48
    request #11676 Components paths in build-manifest should be relative to plugin path c8219c94c1
    User avatar Joris MASSON (jmasson) , 2018-06-25 12:43
    Component paths should be relative to plugin path 75f7c5e2b4
    User avatar Joris MASSON (jmasson) , 2018-06-25 12:51
    Referenced by request #11676

    Artifact Tracker v5

    rel #11517 10.3

    Other

    gerrit #11790
    gerrit #11791
    gerrit #11792
    Display settings

    Follow-ups