karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@apache.org>
Subject Re: The future of gemini-blueprint, take 2 + results
Date Mon, 19 Dec 2016 15:14:00 GMT
2016-12-19 16:12 GMT+01:00 Grzegorz Grzybek <gr.grzybek@gmail.com>:

> Hell,
>
> OK, back to this issue. I built entire Karaf 4.1 with (i)tests using
> "-Dmaven.repo.local=/work/.m2" after removal of gemini-blueprint features
> and repositories. I had to remove hibernate 3.x features as well to make
> the build pass.
>
> The result is (`find .m2 -name _remote.repositories|xargs grep '>'|cut -d
> '>' -f 2|sort|uniq`):
>  - /work/.m2 is 746MB size
>  - there are artifacts from 3 different remote repos:
>     - 1
> (.m2/com/sun/winsw/winsw/1.18/_remote.repositories:winsw-1.18-bin.exe)
> from
> "jenkins"
>     - 2 (org.apache.aries.proxy.impl/1.0.6-SNAPSHOT and
> org.apache.felix.gogo.runtime/1.0.1-SNAPSHOT) from "apache-snapshots"
>     - 882 JARs and 1353 POMs from "central"
>
> Looks good to me. Any last words for gemini/hibernate3?
>

Let them rest in peace...


>
> regards
> Grzegorz
>
> 2016-10-18 6:43 GMT+02:00 David Jencks <david_jencks@yahoo.com.invalid>:
>
> > +1
> >
> > david jencks
> >
> > > On Oct 17, 2016, at 2:33 AM, Grzegorz Grzybek <gr.grzybek@gmail.com>
> > 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
> >
> >
>



-- 
------------------------
Guillaume Nodet
------------------------
Red Hat, Open Source Integration

Email: gnodet@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message