+1 to remove it.
Christian
On 17.10.2016 11:33, Grzegorz Grzybek wrote:
Hello
I've created https://issues.apache.org/jira/browse/KARAF-4774 to consider
deprecation/removal of gemini-blueprint support.
I had this idea after reviewing Maven usage in Karaf4. Currently there's
following configuration of remote repositories:
org.ops4j.pax.url.mvn.repositories= \
http://repo1.maven.org/maven2@id=central, \
http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release,
\
http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external,
\
http://zodiac.springsource.com/maven/bundles/release@id=gemini, \
http://repository.apache.org/content/groups/snapshots-group@id=apache@snapshots@noreleases,
\
https://oss.sonatype.org/content/repositories/snapshots@id=sonatype.snapshots.deploy@snapshots@noreleases,
\
https://oss.sonatype.org/content/repositories/ops4j-snapshots@id=ops4j.sonatype.snapshots.deploy@snapshots@noreleases,
\
http://repository.springsource.com/maven/bundles/external@id=spring-ebr-repository@snapshots@noreleases
4 repositories are SpringSource ones and FAQ on their site says:
*What is the current status of the repository?*
The repository is frozen but will remain accessible *until at least 1
September 2014*. See http://www.eclipse.org/ebr/ for information
regarding the Eclipse Bundle Recipes project to which users of the
SpringSource Enterprise Bundle Repository should transition.
These 4 (3 for non-snapshots) repositories are queried during all
Maven/Aether resolutions.
Maybe it's time to remove gemini-blueprint? What do you think?
best regards
Grzegorz Grzybek
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
