[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-614) Allow Maven URLs to be configured to resolve external bundles

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Fri May 3 05:09:53 EDT 2013


     [ https://issues.jboss.org/browse/JBOSGI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-614.
-----------------------------------

    Resolution: Done


Fixed in jbosgi-repository-3.0.0.CR3

You can now set a property 'org.jboss.osgi.repository.maven.base.urls' with a list of base URL's
                
> Allow Maven URLs to be configured to resolve external bundles
> -------------------------------------------------------------
>
>                 Key: JBOSGI-614
>                 URL: https://issues.jboss.org/browse/JBOSGI-614
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Repository
>    Affects Versions: Continuing
>         Environment: All
>            Reporter: Ulrich Romahn
>            Assignee: Thomas Diesler
>             Fix For: JBossOSGi 2.0.0
>
>
> Currently, JBoss OSGi allows to provide a Maven URI for a package 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 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-osgi-issues mailing list