Tapestry 5
  1. Tapestry 5
  2. TAP5-1469

Allow for multiple application root packages by contributing additional LibraryMappings with empty virtual folder

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      So, the first package is defined in web.xml, but addition ones can be defined as ComponentClassResolver contributions.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        Still good reasons to have the primary package name in web.xml as a single value ... since that is used to search for the AppModule class (that would, in turn, define the other packages).

        Show
        Howard M. Lewis Ship added a comment - Still good reasons to have the primary package name in web.xml as a single value ... since that is used to search for the AppModule class (that would, in turn, define the other packages).
        Hide
        Hudson added a comment -

        Integrated in tapestry-5.2-freestyle #277 (See https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/277/)
        TAP5-1469: Allow for multiple application roto packages by contributing additional LibraryMappings with empty virtual folder

        Show
        Hudson added a comment - Integrated in tapestry-5.2-freestyle #277 (See https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/277/ ) TAP5-1469 : Allow for multiple application roto packages by contributing additional LibraryMappings with empty virtual folder

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development