Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
Description
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.
Attachments
Issue Links
- is related to
-
STANBOL-491 Remove dependencies on third party maven repos
- Closed