Maven 2 & 3

best practices: multi-user installation

Details

  • Number of attachments :
    0

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

Task - A task that needs to be done. MNG-290 Define best practice for using m2 in a shared development environment

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

no features to be done here, just best practices doco (at least for now)

Show
Brett Porter added a comment - no features to be done here, just best practices doco (at least for now)
Hide
Permalink
John Allen added a comment -

Re installers - We deploy our developers java environment via a nice looking NSIS installer (all built using m2 of course) Anyway, that puts in place the m2, then runs (optionally) the JDK, SVN, Tortoise installers and sets up a correct m2/conf/settings and $HOME/.m2 as well as defines MVN_OPTS to ensure the correct keystore info is passed to the JVM so that webdav deployments work. Not hard. And because of the per user env and HOME setup works for multiple users on the same box.

Show
John Allen added a comment - Re installers - We deploy our developers java environment via a nice looking NSIS installer (all built using m2 of course) Anyway, that puts in place the m2, then runs (optionally) the JDK, SVN, Tortoise installers and sets up a correct m2/conf/settings and $HOME/.m2 as well as defines MVN_OPTS to ensure the correct keystore info is passed to the JVM so that webdav deployments work. Not hard. And because of the per user env and HOME setup works for multiple users on the same box.

People

  • Assignee:
    Unassigned
    Reporter:
    Brett Porter
Vote (1)
Watch (3)

Dates

  • Created:
    Updated: