[mng] Allow to use another global settings than the one in the conf directory of the maven installation

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 0.9.4
  • Fix Version/s: None
  • Component/s: Help Wanted, Maven Embedder
  • Labels:
    None

Description

Global settings are by default set to MAVEN_INSTALL_DIR\conf\settings.xml and we cannot change it.
We can do it in the comand line of maven with -Dorg.apache.maven.global-settings=...
In our case we use it to store environment settings (repositories & co)
Users settings are used for private data used by developpers (credentials & co).
Extracting global settings from maven installation help us to change maven releases without modifying the original packaging.

  1. Text File
    m2e-global-settings.patch
    28/Aug/08 9:57 AM
    9 kB
    Eugene Kuleshov

Issue Links

depends upon

New Feature - A new feature of the product, which has yet to be developed. MNG-3611 allow to pass in location of global settings file to maven cli

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MNGECLIPSE-877 allow alternate location of global settings file

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

New Feature - A new feature of the product, which has yet to be developed. MNG-3914 Add CLI option to control location of global settings from command line

  • 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
John Casey added a comment -

Starting in Maven 2.1 (the snapshots of which are used by m2eclipse), there are two ways to achieve this:

1. you can set the location of the global settings file in the MavenExecutionRequest.setGlobalSettingsFile(..) method, and then pass it into the embedder instance.
2. If you're using an external maven installation - and this works in 2.0.x - you can use the approach that Arnaud suggested: -Dorg.apache.maven.global-settings=/path/to/settings.xml

Show
John Casey added a comment - Starting in Maven 2.1 (the snapshots of which are used by m2eclipse), there are two ways to achieve this: 1. you can set the location of the global settings file in the MavenExecutionRequest.setGlobalSettingsFile(..) method, and then pass it into the embedder instance. 2. If you're using an external maven installation - and this works in 2.0.x - you can use the approach that Arnaud suggested: -Dorg.apache.maven.global-settings=/path/to/settings.xml
Hide
Permalink
Eugene Kuleshov added a comment -

Thanks John. The problem I have is with Maven 2.1 runing out of the process. We are using MavenCli class to start Maven, so #1 is not an option and from your response it is unclear is #2 is going to work with Maven 2.1 either. Anyways, it doesn't look like this is a standard way to specify global settings and I've opened

Arnaud, currently global settings are only used with external Maven runtime and always from a standard place, such as MAVEN_HOME/conf/settings.xml

It is unclear to me if we can address this until MNG-3611 is resolved in both Maven 2.0 and 2.1

Show
Eugene Kuleshov added a comment - Thanks John. The problem I have is with Maven 2.1 runing out of the process. We are using MavenCli class to start Maven, so #1 is not an option and from your response it is unclear is #2 is going to work with Maven 2.1 either. Anyways, it doesn't look like this is a standard way to specify global settings and I've opened Arnaud, currently global settings are only used with external Maven runtime and always from a standard place, such as MAVEN_HOME/conf/settings.xml It is unclear to me if we can address this until MNG-3611 is resolved in both Maven 2.0 and 2.1
Hide
Permalink
Eugene Kuleshov added a comment -

I took a closer look at this and apparently org.apache.maven.global-settings property is not respected by Maven 2.1-SNAPSHOT currently used by m2eclipse, nor by 3.0-SNAPSHOT from trunk. So, we can't reliably use this property without further confusion.

Show
Eugene Kuleshov added a comment - I took a closer look at this and apparently org.apache.maven.global-settings property is not respected by Maven 2.1-SNAPSHOT currently used by m2eclipse, nor by 3.0-SNAPSHOT from trunk. So, we can't reliably use this property without further confusion.
Hide
Permalink
Eugene Kuleshov added a comment -

Here is half-working patch that uses suggested property.

Show
Eugene Kuleshov added a comment - Here is half-working patch that uses suggested property.
Hide
Permalink
Arnaud Heritier added a comment -

Perhaps MNG-3914 can help to solve it ??

Show
Arnaud Heritier added a comment - Perhaps MNG-3914 can help to solve it ??

People

  • Assignee:
    Unassigned
    Reporter:
    Arnaud Heritier
Vote (7)
Watch (4)

Dates

  • Created:
    Updated: