Maven
  1. Maven
  2. MNG-367

best practices: multi-user installation

    Details

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

      Description

      so we need to support:

      • read only install
      • setttings in the installation
      • works with just the m2 executable in the path (no M2_HOME setting)
      • possibility of a remote settings file for standalone installs, force a regular (daily) check when online to push updates

      encourage:

      • storing of install on a shared, read only drive
      • possibly use a CVS checkout
      • may want to integrate with existing deployment policies (eg an MSI that can be easily deployed)

        Issue Links

          Activity

          Brett Porter created issue -
          Brett Porter made changes -
          Field Original Value New Value
          Link This issue duplicates MNG-290 [ MNG-290 ]
          Vincent Massol made changes -
          Workflow jira [ 33985 ] Maven [ 37175 ]
          Brett Porter made changes -
          Fix Version/s 2.0-beta-1 [ 11040 ]
          Description so we need to support:
          - read only install
          - setttings in the installation
          - works with just the m2 executable in the path (no M2_HOME setting)
          - possibility of a remote settings file for standalone installs, force a regular (daily) check when online to push updates

          encourage:
          - storing of install on a shared, read only drive
          - possibly use a CVS checkout
          - may want to integrate with existing deployment policies (eg an MSI that can be easily deployed)



          so we need to support:
          - read only install
          - setttings in the installation
          - works with just the m2 executable in the path (no M2_HOME setting)
          - possibility of a remote settings file for standalone installs, force a regular (daily) check when online to push updates

          encourage:
          - storing of install on a shared, read only drive
          - possibly use a CVS checkout
          - may want to integrate with existing deployment policies (eg an MSI that can be easily deployed)



          Fix Version/s 2.0-beta-2 [ 11861 ]
          Environment
          Brett Porter made changes -
          Fix Version/s 2.0-beta-3 [ 12015 ]
          Fix Version/s 2.0-beta-2 [ 11861 ]
          Brett Porter made changes -
          Fix Version/s 2.0 [ 11703 ]
          Component/s documentation [ 11342 ]
          Fix Version/s 2.0-beta-3 [ 12015 ]
          Jason van Zyl made changes -
          Component/s best practices [ 11896 ]
          Component/s design [ 11341 ]
          Component/s documentation - general [ 11342 ]
          Jason van Zyl made changes -
          Description so we need to support:
          - read only install
          - setttings in the installation
          - works with just the m2 executable in the path (no M2_HOME setting)
          - possibility of a remote settings file for standalone installs, force a regular (daily) check when online to push updates

          encourage:
          - storing of install on a shared, read only drive
          - possibly use a CVS checkout
          - may want to integrate with existing deployment policies (eg an MSI that can be easily deployed)



          so we need to support:
          - read only install
          - setttings in the installation
          - works with just the m2 executable in the path (no M2_HOME setting)
          - possibility of a remote settings file for standalone installs, force a regular (daily) check when online to push updates

          encourage:
          - storing of install on a shared, read only drive
          - possibly use a CVS checkout
          - may want to integrate with existing deployment policies (eg an MSI that can be easily deployed)



          Environment
          Summary best practices: multi-user deployment of a maven2 install best practices: multi-user installation
          John Casey made changes -
          Fix Version/s 2.0.1 [ 12000 ]
          Fix Version/s 2.0.2 [ 12107 ]
          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 ]
          John Casey made changes -
          Fix Version/s 2.0.3 [ 12107 ]
          Fix Version/s 2.1 [ 11704 ]
          Vincent Massol made changes -
          Workflow Maven [ 37175 ] Maven New [ 47607 ]
          Jason van Zyl made changes -
          Fix Version/s 2.1.x [ 13142 ]
          Fix Version/s 2.1 [ 11704 ]
          Brett Porter made changes -
          Fix Version/s 2.1 [ 13142 ]
          Fix Version/s Documentation Deficit [ 13554 ]
          Jason van Zyl made changes -
          Resolution Incomplete [ 4 ]
          Status Open [ 1 ] Closed [ 6 ]
          Michael Osipov made changes -
          Fix Version/s Documentation Deficit [ 13554 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
          Mark Thomas made changes -
          Workflow jira [ 12711720 ] Default workflow, editable Closed status [ 12751624 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
          Mark Thomas made changes -
          Workflow jira [ 12949064 ] Default workflow, editable Closed status [ 12988346 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development