I have a general question for this community:

Currently, JBoss OSGi allows to provide a Maven URI in standalone.xml or  domain.xml for a bunle which will then be resolved by the deployer according to the following rules:
1. check if the artifact is present in a local Maven repo (.m2)
2. if not, download the artifact from a remote Maven repo

Currently, the class MavenArtifactRepository which appears to be responsible for the second path mentioned above has two Maven repository URLs hardcoded:
JBOSS_NEXUS_BASE = "http://repository.jboss.org/nexus/content/groups/public";
MAVEN_CENTRAL_BASE = "http://repo1.maven.org/maven2";

It should be possible to configure those URLs using some configuration mechanism. This is especially important in a real production environment where access to external URLs may be blocked by a firewall and an internal Nexus repo should be used to proxy a "stable set" of artifacts to be used for production.

The following configuration options should be possible:
1. as it is right now
2. switch off external resolution completely. Only artifacts currently present on the local filesystem (.m2) should be resolved and loaded
3. Configure Maven URLs in addition to the hardcoded ones above
4. Configure Maven URLs as complete replacements to the hardcoded ones above

Is this something we should have?

I already created a JIRA for this (https://issues.jboss.org/browse/JBOSGI-614).

If we would implement this, what would be the best way to provide the configuration?