[MNG-367] best practices: multi-user installation

• Type: Task
• Status: Closed
• Priority: Trivial
• Resolution: Incomplete
• Component/s: Design, Patterns & Best Practices
• Assignee: Unassigned
• Reporter: Brett Porter
• Created: 04/May/05 10:01
• Updated: 31/Jan/15 13:35
• Resolved: 19/Jan/14 15:02

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

• duplicates: MNG-290 Define best practice for using m2 in a shared development environment