Comment 1 Igor Fedorenko 2011-02-22 17:39:39 EST

Please provide complete user story so we understand who and under what circumstances might want to change discovery URL.

Comment 2 Michael Mising name 2011-08-24 19:05:52 EDT

I agree. I have an issue ongoing at the moment where I can't access the discovery catalog because of a proxy issue.  I wanted to configure the url to a local hosted version, or just to another xml file so I could redirect to a custom jar.  I think it shouldn't be easily configurable, if that's your concern, but at least make it a property.

Comment 3 Fred Bricon 2012-02-29 05:15:38 EST

Igor,

in order to test changes to the discovery catalog, I found it convenient to change  the hardcoded PATH value in MavenDiscovery.java to 

  public static final String PATH;
  
  static {
    String defaultPath = "http://download.eclipse.org/technology/m2e/discovery/directory-1.1.xml"; //$NON-NLS-1$ 
    PATH = System.getProperty("m2e.discovery.url", defaultPath); //$NON-NLS-1$
  }

That allows me to easily test upcoming changes in the catalog with a JVM property like -Dm2e.discovery.url=file:/D:/directory.xml

Are you ok for me to push that change?

Comment 4 Igor Fedorenko 2012-02-29 10:23:19 EST

Yes, this looks okay, just use "public static final String DEFAULT_URL =..." for the default url ;-)

Comment 5 Fred Bricon 2012-02-29 11:25:57 EST

Fixed using an environment variable. Alternate discovery URLs can be used by launching eclipse with : 
-Dm2e.discovery.url=/some/url/

Comment 6 Denis Roy 2021-04-19 13:22:26 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/