Maven
  1. Maven
  2. MNG-416

best practices: multiple profile deployments

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      There have been several threads on the user and dev list following on from the recommendations made in the best practices document.

      The objective is to make an artifact standalone, without the need to rebuild to deploy to a new environment. Configuration should be externalised (or all stored inside and selected based on an externalised parameter). This can usually be done with JNDI in J2EE (especially for database configurations), but this has a couple of limitations:

      • JNDI can be awkward and may not be available outside of the container (though directory-naming can be used)
      • some things in the deployment descriptor must be inside the artifact, but need to be different between environments (eg security settings in web.xml and a bunch of weblogic specific files for which the container does not provide external/admin based configuration for).

      Some products to consider:

        Activity

        Brett Porter created issue -
        Vincent Massol made changes -
        Field Original Value New Value
        Workflow jira [ 34295 ] Maven [ 36811 ]
        Jason van Zyl made changes -
        Environment
        Summary recommend a best practice/plugin for multiple profile deployment best practices: multiple profile deployments
        Description There have been several threads on the user and dev list following on from the recommendations made in the best practices document.

        The objective is to make an artifact standalone, without the need to rebuild to deploy to a new environment. Configuration should be externalised (or all stored inside and selected based on an externalised parameter). This can usually be done with JNDI in J2EE (especially for database configurations), but this has a couple of limitations:
        - JNDI can be awkward and may not be available outside of the container (though directory-naming can be used)
        - some things in the deployment descriptor must be inside the artifact, but need to be different between environments (eg security settings in web.xml and a bunch of weblogic specific files for which the container does not provide external/admin based configuration for).

        Some products to consider:
        - payload/genesis: http://www.osjava.org/payload/
        - easyconf: http://easyconf.sourceforge.net/index.html
        There have been several threads on the user and dev list following on from the recommendations made in the best practices document.

        The objective is to make an artifact standalone, without the need to rebuild to deploy to a new environment. Configuration should be externalised (or all stored inside and selected based on an externalised parameter). This can usually be done with JNDI in J2EE (especially for database configurations), but this has a couple of limitations:
        - JNDI can be awkward and may not be available outside of the container (though directory-naming can be used)
        - some things in the deployment descriptor must be inside the artifact, but need to be different between environments (eg security settings in web.xml and a bunch of weblogic specific files for which the container does not provide external/admin based configuration for).

        Some products to consider:
        - payload/genesis: http://www.osjava.org/payload/
        - easyconf: http://easyconf.sourceforge.net/index.html
        Jason van Zyl made changes -
        Component/s maven-plugins [ 11380 ]
        Component/s design [ 11341 ]
        Component/s documentation - general [ 11342 ]
        Component/s best practices [ 11896 ]
        John Casey made changes -
        Fix Version/s 2.0.2 [ 12107 ]
        Fix Version/s 2.0.1 [ 12000 ]
        Jason van Zyl made changes -
        Component/s design [ 11341 ]
        Component/s documentation - best practices [ 11896 ]
        Jason van Zyl made changes -
        Priority Major [ 3 ] Trivial [ 5 ]
        Jason van Zyl made changes -
        Fix Version/s 2.0.3 [ 12107 ]
        Fix Version/s 2.1.1 [ 12292 ]
        Jason van Zyl made changes -
        Fix Version/s 2.0.4 [ 12294 ]
        Fix Version/s 2.1.1 [ 12292 ]
        Vincent Massol made changes -
        Workflow Maven [ 36811 ] Maven New [ 48042 ]
        John Casey made changes -
        Fix Version/s 2.0.5 [ 12294 ]
        John Casey made changes -
        Fix Version/s 2.2 [ 12081 ]
        Jason van Zyl made changes -
        Fix Version/s 2.2 [ 12081 ]
        Fix Version/s 2.2.x [ 13145 ]
        Jason van Zyl made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Incomplete [ 4 ]
        Paul Benedict made changes -
        Fix Version/s Issues to be reviewed for 3.x [ 13145 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
        Mark Thomas made changes -
        Workflow jira [ 12711756 ] Default workflow, editable Closed status [ 12751711 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
        Mark Thomas made changes -
        Workflow jira [ 12949095 ] Default workflow, editable Closed status [ 12988395 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Brett Porter
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development