subject:"The future of gemini\-blueprint"

Re: The future of gemini-blueprint, take 2 + results

2016-12-19 Thread Andrea Cosentino

+1. 
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, December 19, 2016 4:12 PM, Grzegorz Grzybek  
wrote:
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?

regards
Grzegorz

2016-10-18 6:43 GMT+02:00 David Jencks :

> +1
>
> david jencks
>
> > On Oct 17, 2016, at 2:33 AM, 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
>
>

Re: The future of gemini-blueprint, take 2 + results

2016-12-19 Thread Jean-Baptiste Onofré


Bye ;)

Regards
JB

On 12/19/2016 04:12 PM, Grzegorz Grzybek wrote:

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?

regards
Grzegorz

2016-10-18 6:43 GMT+02:00 David Jencks :


+1

david jencks


On Oct 17, 2016, at 2:33 AM, 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







--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: The future of gemini-blueprint, take 2 + results

2016-12-19 Thread Grzegorz Grzybek

Amen | Żegnajcie | Goodbye then

regards
Grzegorz

2016-12-19 16:14 GMT+01:00 Guillaume Nodet :

> 2016-12-19 16:12 GMT+01:00 Grzegorz Grzybek :
>
> > 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 :
> >
> > > +1
> > >
> > > david jencks
> > >
> > > > On Oct 17, 2016, at 2:33 AM, 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
> > >
> > >
> >
>
>
>
> --
> 
> Guillaume Nodet
> 
> Red Hat, Open Source Integration
>
> Email: gno...@redhat.com
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>

Re: The future of gemini-blueprint, take 2 + results

2016-12-19 Thread Guillaume Nodet

2016-12-19 16:12 GMT+01:00 Grzegorz Grzybek :

> 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 :
>
> > +1
> >
> > david jencks
> >
> > > On Oct 17, 2016, at 2:33 AM, 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
> >
> >
>



-- 

Guillaume Nodet

Red Hat, Open Source Integration

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

The future of gemini-blueprint, take 2 + results

2016-12-19 Thread Grzegorz Grzybek

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?

regards
Grzegorz

2016-10-18 6:43 GMT+02:00 David Jencks :

> +1
>
> david jencks
>
> > On Oct 17, 2016, at 2:33 AM, 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
>
>

Re: The future of gemini-blueprint

2016-10-17 Thread David Jencks

+1

david jencks

> On Oct 17, 2016, at 2:33 AM, 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

Re: The future of gemini-blueprint

2016-10-17 Thread Freeman Fang

+1

Thanks!
－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat



> On Oct 17, 2016, at 5:33 PM, 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

Re: The future of gemini-blueprint

2016-10-17 Thread Achim Nierbeck

+1

regards, Achim

2016-10-17 12:36 GMT+02:00 Sobkowiak Krzysztof :

> +1 (non-binding)
>
> Regards
> Krzysztof
>
> 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
> >
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.
> pl/)
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

Re: The future of gemini-blueprint

2016-10-17 Thread Sobkowiak Krzysztof

+1 (non-binding)

Regards
Krzysztof

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
>

-- 
Krzysztof Sobkowiak

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)

Re: The future of gemini-blueprint

2016-10-17 Thread Jean-Baptiste Onofré


+1

Regards
JB

On 10/17/2016 11:33 AM, 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



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: The future of gemini-blueprint

2016-10-17 Thread Guillaume Nodet

+1 we should remove any reference to the old spring repos

Fwiw, there has been a 2.0.0.RELEASE version of gemini blueprint released
last april and the related artifacts are available from maven central.
With the spring namespaces now being supported by aries blueprint, I think
we should get rid of the gemini ones.


2016-10-17 11:33 GMT+02:00 Grzegorz Grzybek :

> 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: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: The future of gemini-blueprint

2016-10-17 Thread Andrea Cosentino

+1 (non-binding) to remove it.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, October 17, 2016 11:42 AM, Christian Schneider 
 wrote:
+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

Re: The future of gemini-blueprint

2016-10-17 Thread Christian Schneider


+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

The future of gemini-blueprint

2016-10-17 Thread Grzegorz Grzybek

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

Re: The future of gemini-blueprint, take 2 + results

Re: The future of gemini-blueprint, take 2 + results

Re: The future of gemini-blueprint, take 2 + results

Re: The future of gemini-blueprint, take 2 + results

The future of gemini-blueprint, take 2 + results

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

Re: The future of gemini-blueprint

The future of gemini-blueprint

14 matches

Site Navigation

Mail list logo

Footer information