Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-5209

Further standardize and preconfigure default and required dependencies for Hippo based projects

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 2.20.00
    • None

    Description

      Standard and assumed provided dependencies for all Hippo projects extending from hippo-cms7-project:

      • geronimo-jta_1.1_spec-1.1.jar
      • jcr-2.0.jar
      • jdo2-api-2.3-eb.jar
      • mail-2.4.3.jar

      As predefined container-wide dependencies, these will be pre-configured for cargo to the deployed to tomcat common/lib.
      Furthermore, in the website-archetype and gogreen assembly distribution.xml these predefined dependencies are not packaged anymore in a distribution
      as they are presumed (required) to be provided by the container itself (on the common/lib classpath).
      The Hippo and application specific shared dependencies, like hippo-repository-api, hst-api, hst-common, workflow common etc. is what remains to be deployed to shared/lib and therefore packaged
      with every release.

      Tasks:

      • update cms7-project-pom for the above
      • update website archetype for the above
      • update gogreen and hst demosuite and possible other example or test projects for the above
      • remove activation and mail dependency definitions from all cms7-project-pom extending projects

      Note: none of the above should have any technical impact, its merely further standardization and cleanup of redundant project configurations.

      Attachments

        Activity

          People

            jsheriff Junaidh Kadhar Sheriff
            adouma Ate Douma
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: