[jira] [Commented] (STANBOL-510) Metaxa engine uses dependencies from third party repositories

["Walter Kasper (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STANBOL-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218182#comment-13218182 ] 

Walter Kasper commented on STANBOL-510:
---------------------------------------

We contacted the Aperture developers, and in general they have no objections to add Aperture to Maven central. But they do have problems with some inflexibility in Apache's release policies, such as the use of snapshots or not released versions of components for bug fixes. Here is an excerpt from the Aperture reply:

> The question of deploying Aperture in Maven Central has been popping up on the developer mailing list for years. We haven't done it because the majority of the "active" user community used Aperture and all its libraries as a black box. Therefore "a bug in Aperture" often boiled down to a bug in poi/pdfbox/mstor/ical4j/younameit. For this reason I have been maintaining the aperture maven repository, and deployed the versions of external dependencies that contained all the latest and greatest fixes.
> 
> Apache Foundation and the folks who manage the Maven Central repository seem to have much more strict policies in this respect. For instance, whenever a Tika user reports a bug in POI, first it's fixed in POI, then they wait for a POI release, update the dependency in Tika and wait for a Tika release. This obviously has many advantages, yet for our purposes, such rigidity would make life very difficult.
> 
> Thinks have changed lately though. I would personally be very happy to accept input on how to improve things in this respect. Most importantly:
>
> 1. Which non-released aperture dependencies can safely be replaced with released versions.
>  2. Which of those who don't, need to be released first (RDF2Go springs to mind, yet there may be more).
>  3. From those in 1 and 2 which aren't present in Maven Central yet and must be deployed there first.
>  4. Then we can release Aperture 1.7.
 > 5. ... and push it to Maven Central.

So there seems to be more involved than just uploading some jars to Maven central.
                
> Metaxa engine uses dependencies from third party repositories
> -------------------------------------------------------------
>
>                 Key: STANBOL-510
>                 URL: https://issues.apache.org/jira/browse/STANBOL-510
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Enhancer
>            Reporter: Fabian Christ
>            Assignee: Walter Kasper
>              Labels: Dependencies, Repository
>
> The Metaxa engine currently configures the following repos in its POM
>   <repositories>
>     <repository>
>       <releases>
>         <enabled>true</enabled>
>       </releases>
>       <snapshots>
>         <enabled>false</enabled>
>       </snapshots>
>       <id>aduna-opensource.releases</id>
>       <name>Aduna Open Source - Maven releases</name>
>       <url>http://repo.aduna-software.org/maven2/releases</url>
>     </repository>
>     <repository>
>       <releases>
>         <enabled>true</enabled>
>         <updatePolicy>never</updatePolicy>
>       </releases>
>       <snapshots>
>         <enabled>false</enabled>
>       </snapshots>
>       <id>aperture-repo</id>
>       <name>Aperture Dependencies Repo</name>
>       <url>http://aperture.sourceforge.net/maven/</url>
>     </repository>
>     <repository>
>       <releases>
>         <enabled>true</enabled>
>         <updatePolicy>never</updatePolicy>
>       </releases>
>       <snapshots>
>         <enabled>false</enabled>
>       </snapshots>
>       <id>dfki-lt-repo</id>
>       <name>DFKI LT Repository</name>
>       <url>http://www.dfki.de/~kasper/IKS/maven</url>
>     </repository>
>   </repositories>
> Those repos need to be removed and all used artifacts need to be available via the Maven central repository. Otherwise is the Metaxa engine not releasable according to the Apache release policy.

--
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