You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/04 17:02:19 UTC
[jira] Created: (MNG-367) best practices: multi-user deployment of a maven2 install
best practices: multi-user deployment of a maven2 install
---------------------------------------------------------
Key: MNG-367
URL: http://jira.codehaus.org/browse/MNG-367
Project: m2
Type: Task
Components: design
Reporter: Brett Porter
Fix For: 2.0-beta-1
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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user installation
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Jason van Zyl updated MNG-367:
------------------------------
Priority: Trivial (was: Major)
> best practices: multi-user installation
> ---------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Priority: Trivial
> Fix For: 2.0.3
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user installation
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
John Casey updated MNG-367:
---------------------------
Fix Version: (was: 2.0.1)
2.0.2
> best practices: multi-user installation
> ---------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: documentation - best practices
> Reporter: Brett Porter
> Fix For: 2.0.2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user deployment of a maven2 install
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Brett Porter updated MNG-367:
-----------------------------
Fix Version: (was: 2.0-beta-3)
2.0
Component: documentation
no features to be done here, just best practices doco (at least for now)
> best practices: multi-user deployment of a maven2 install
> ---------------------------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: documentation, design
> Reporter: Brett Porter
> Fix For: 2.0
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user installation
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Jason van Zyl updated MNG-367:
------------------------------
Component: (was: documentation - best practices)
design
> best practices: multi-user installation
> ---------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Fix For: 2.0.3
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user deployment of a maven2 install
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Brett Porter updated MNG-367:
-----------------------------
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)
was:
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: (was: 2.0-beta-1)
2.0-beta-2
Environment:
> best practices: multi-user deployment of a maven2 install
> ---------------------------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Fix For: 2.0-beta-2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user deployment of a maven2 install
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Jason van Zyl updated MNG-367:
------------------------------
Component: (was: design)
(was: documentation - general)
best practices
> best practices: multi-user deployment of a maven2 install
> ---------------------------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: best practices
> Reporter: Brett Porter
> Fix For: 2.0.1
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user installation
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
John Casey updated MNG-367:
---------------------------
Fix Version: (was: 2.0.3)
2.1
> best practices: multi-user installation
> ---------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Brett Porter
> Priority: Trivial
> Fix For: 2.1
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-367) best practices: multi-user installation
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-367?page=all ]
Jason van Zyl updated MNG-367:
------------------------------
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)
was:
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 installation (was: best practices: multi-user deployment of a maven2 install)
> best practices: multi-user installation
> ---------------------------------------
>
> Key: MNG-367
> URL: http://jira.codehaus.org/browse/MNG-367
> Project: Maven 2
> Type: Task
> Components: best practices
> Reporter: Brett Porter
> Fix For: 2.0.1
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org