[jira] [Resolved] (STANBOL-491) Remove dependencies on third party maven repos

["Fabian Christ (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STANBOL-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Christ resolved STANBOL-491.
-----------------------------------

    Resolution: Fixed

All third party POMs are removed for released artifacts. The only exception is the metaxa engine which will be excluded from the release.
                
> Remove dependencies on third party maven repos
> ----------------------------------------------
>
>                 Key: STANBOL-491
>                 URL: https://issues.apache.org/jira/browse/STANBOL-491
>             Project: Stanbol
>          Issue Type: Task
>            Reporter: Reto Bachmann-Gmür
>
> See http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/ to learn why there shouldn't be dependencies to third party repos.
> Ideally we convince the upstream developers to push their artifacts to maven central. Alternatively we can follow https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository.
> If both fails I think we can have the dependencies in SVN as this is done for reasoners/hermit. When choosing this approach the maven bundle plugin should be configured to include the dependencies in the bundle as it is otherwise required at runtime or when building the launcher as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira