9:53 a.m.
Hi,
I've noticed that Keycloak Maven artifacts are not synced to Maven Central,
they are only on JBoss Nexus. Do you plan to sync them to Central?
Let me know if so, I can help with that.
Karel
11:22 a.m.
That'd be great
----- Original Message -----
From: "Karel Piwko" <kpiwko(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 30 January, 2014 8:53:45 AM
Subject: [keycloak-dev] Keycloak artifacts not in Maven Central
Hi,
I've noticed that Keycloak Maven artifacts are not synced to Maven Central,
they are only on JBoss Nexus. Do you plan to sync them to Central?
Let me know if so, I can help with that.
Karel
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
2:13 p.m.
I did some checks and there is some work needed:
1/ According to Maven Central rules, there should not be any <repository>
elements in pom.xml files
2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
available no Maven Central
So, following steps are needed:
* figure out whether jbossweb dependency could be replaced by something else,
if not - it has to undergo same checks as keycloak and be synced to Maven
Central or, which I prefer, to release it relocated to org.keycloak groupId.
Given that 7.0.17.Final has do external dependencies at all -
seems much easier then trying to convince sonatype to pick a single version
of jbossweb tree
* remove all <repositories> from pom.xml files
Then, 1.0-alpha-2 and further releases can be synced to Maven Central. Sonatype
might apply more rules but project looks in good shape Maven-wise IMO.
Karel
On Thu, 30 Jan 2014 05:22:07 -0500 (EST)
Stian Thorgersen <stian(a)redhat.com> wrote:
That'd be great
----- Original Message -----
> From: "Karel Piwko" <kpiwko(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Thursday, 30 January, 2014 8:53:45 AM
> Subject: [keycloak-dev] Keycloak artifacts not in Maven Central
>
> Hi,
>
> I've noticed that Keycloak Maven artifacts are not synced to Maven Central,
> they are only on JBoss Nexus. Do you plan to sync them to Central?
>
> Let me know if so, I can help with that.
>
> Karel
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
2:20 p.m.
I don't know how to do that actually...I thought it was something Nexus
did automatically.
On 1/30/2014 3:53 AM, Karel Piwko wrote:
Hi,
I've noticed that Keycloak Maven artifacts are not synced to Maven Central,
they are only on JBoss Nexus. Do you plan to sync them to Central?
Let me know if so, I can help with that.
Karel
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
2:37 p.m.
On 1/30/2014 8:13 AM, Karel Piwko wrote:
I did some checks and there is some work needed:
1/ According to Maven Central rules, there should not be any <repository>
elements in pom.xml files
2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is
not
available no Maven Central
So, following steps are needed:
* figure out whether jbossweb dependency could be replaced by something else,
if not - it has to undergo same checks as keycloak and be synced to Maven
Central or, which I prefer, to release it relocated to org.keycloak groupId.
Given that 7.0.17.Final has do external dependencies at all -
seems much easier then trying to convince sonatype to pick a single version
of jbossweb tree
* remove all <repositories> from pom.xml files
Would hosting at Maven Central require developers to configure their
settings.xml, or can the build still run OOTB? A build running OOTB is
more important than hosting at Maven Central.
Also, what is the performance of Maven Central compared to
repository.jboss.org? I've often had slow as balls connections to Maven
Central and never any problems with repository.jboss.org. Finally,
nobody has ever complained that Resteasy is not at Maven central.
People have no problems using repository.jboss.org so I don't see what
the big deal is.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
2:45 p.m.
Hosting on Maven Central means that folks can use Keycloak artifaces without having to add
JBoss Nexus to their poms. So IMO it makes it slightly simpler to add Keycloak deps.
RestEasy is on Maven Central (http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 30 January, 2014 1:37:47 PM
Subject: Re: [keycloak-dev] Keycloak artifacts not in Maven Central
On 1/30/2014 8:13 AM, Karel Piwko wrote:
> I did some checks and there is some work needed:
>
> 1/ According to Maven Central rules, there should not be any <repository>
> elements in pom.xml files
> 2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
> available no Maven Central
>
> So, following steps are needed:
>
> * figure out whether jbossweb dependency could be replaced by something
> else,
> if not - it has to undergo same checks as keycloak and be synced to
> Maven
> Central or, which I prefer, to release it relocated to org.keycloak
> groupId.
> Given that 7.0.17.Final has do external dependencies at all -
> seems much easier then trying to convince sonatype to pick a single
> version
> of jbossweb tree
> * remove all <repositories> from pom.xml files
>
Would hosting at Maven Central require developers to configure their
settings.xml, or can the build still run OOTB? A build running OOTB is
more important than hosting at Maven Central.
Also, what is the performance of Maven Central compared to
repository.jboss.org? I've often had slow as balls connections to Maven
Central and never any problems with repository.jboss.org. Finally,
nobody has ever complained that Resteasy is not at Maven central.
People have no problems using repository.jboss.org so I don't see what
the big deal is.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
2:47 p.m.
On 1/30/2014 8:45 AM, Stian Thorgersen wrote:
Hosting on Maven Central means that folks can use Keycloak artifaces
without having to add JBoss Nexus to their poms. So IMO it makes it slightly simpler to
add Keycloak deps.
RestEasy is on Maven Central (http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
??? It has the same pom and dependency issues as keycloak!
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
3:30 p.m.
Correct, Maven Central is even simpler to use. Works ootb, no mangling with
settings.xml is required at all.
I asked for pushing RESTEasy to Maven Central in Nov 2011, needed for EAP6/WFK2.
There was the same clean up of pom.xml(s) back then.
Performance wise, I have no idea. I'm not experiencing any difference at all. If
you experience connection lags, you can always mirror Maven Central to a
different repo, such as JBoss Nexus -
http://maven.apache.org/guides/mini/guide-mirror-settings.html.
Karel
On Thu, 30 Jan 2014 08:45:20 -0500 (EST)
Stian Thorgersen <stian(a)redhat.com> wrote:
Hosting on Maven Central means that folks can use Keycloak artifaces
without
having to add JBoss Nexus to their poms. So IMO it makes it slightly simpler
to add Keycloak deps.
RestEasy is on Maven Central
(http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Thursday, 30 January, 2014 1:37:47 PM
> Subject: Re: [keycloak-dev] Keycloak artifacts not in Maven Central
>
>
>
> On 1/30/2014 8:13 AM, Karel Piwko wrote:
> > I did some checks and there is some work needed:
> >
> > 1/ According to Maven Central rules, there should not be any
<repository>
> > elements in pom.xml files
>
>
> > 2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
> > available no Maven Central
> >
> > So, following steps are needed:
> >
> > * figure out whether jbossweb dependency could be replaced by something
> > else,
> > if not - it has to undergo same checks as keycloak and be synced to
> > Maven
> > Central or, which I prefer, to release it relocated to org.keycloak
> > groupId.
> > Given that 7.0.17.Final has do external dependencies at all -
> > seems much easier then trying to convince sonatype to pick a single
> > version
> > of jbossweb tree
> > * remove all <repositories> from pom.xml files
> >
>
> Would hosting at Maven Central require developers to configure their
> settings.xml, or can the build still run OOTB? A build running OOTB is
> more important than hosting at Maven Central.
>
> Also, what is the performance of Maven Central compared to
> repository.jboss.org? I've often had slow as balls connections to Maven
> Central and never any problems with repository.jboss.org. Finally,
> nobody has ever complained that Resteasy is not at Maven central.
> People have no problems using repository.jboss.org so I don't see what
> the big deal is.
>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
4:17 p.m.
Resteasy 3.0.6 master pom (downloaded from maven central) has
repository.jboss.org as a repository and also has a jboss-web dependency
so I don't understand why Keycloak can't be pushed to maven central.
On 1/30/2014 9:30 AM, Karel Piwko wrote:
Correct, Maven Central is even simpler to use. Works ootb, no
mangling with
settings.xml is required at all.
I asked for pushing RESTEasy to Maven Central in Nov 2011, needed for EAP6/WFK2.
There was the same clean up of pom.xml(s) back then.
Performance wise, I have no idea. I'm not experiencing any difference at all. If
you experience connection lags, you can always mirror Maven Central to a
different repo, such as JBoss Nexus -
http://maven.apache.org/guides/mini/guide-mirror-settings.html.
Karel
On Thu, 30 Jan 2014 08:45:20 -0500 (EST)
Stian Thorgersen <stian(a)redhat.com> wrote:
> Hosting on Maven Central means that folks can use Keycloak artifaces without
> having to add JBoss Nexus to their poms. So IMO it makes it slightly simpler
> to add Keycloak deps.
>
> RestEasy is on Maven Central
> (http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
>
> ----- Original Message -----
>> From: "Bill Burke" <bburke(a)redhat.com>
>> To: keycloak-dev(a)lists.jboss.org
>> Sent: Thursday, 30 January, 2014 1:37:47 PM
>> Subject: Re: [keycloak-dev] Keycloak artifacts not in Maven Central
>>
>>
>>
>> On 1/30/2014 8:13 AM, Karel Piwko wrote:
>>> I did some checks and there is some work needed:
>>>
>>> 1/ According to Maven Central rules, there should not be any
<repository>
>>> elements in pom.xml files
>>
>>
>>> 2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
>>> available no Maven Central
>>>
>>> So, following steps are needed:
>>>
>>> * figure out whether jbossweb dependency could be replaced by something
>>> else,
>>> if not - it has to undergo same checks as keycloak and be synced to
>>> Maven
>>> Central or, which I prefer, to release it relocated to org.keycloak
>>> groupId.
>>> Given that 7.0.17.Final has do external dependencies at all -
>>> seems much easier then trying to convince sonatype to pick a single
>>> version
>>> of jbossweb tree
>>> * remove all <repositories> from pom.xml files
>>>
>>
>> Would hosting at Maven Central require developers to configure their
>> settings.xml, or can the build still run OOTB? A build running OOTB is
>> more important than hosting at Maven Central.
>>
>> Also, what is the performance of Maven Central compared to
>> repository.jboss.org? I've often had slow as balls connections to Maven
>> Central and never any problems with repository.jboss.org. Finally,
>> nobody has ever complained that Resteasy is not at Maven central.
>> People have no problems using repository.jboss.org so I don't see what
>> the big deal is.
>>
>>
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
4:31 p.m.
Quoting
http://maven.apache.org/guides/mini/guide-central-repository-upload.html -
Q: I have other repositories or pluginRepositories listed in my POM, is that a
problem?
A: At present, this won't preclude your project from being included,
but we do strongly encourage making sure all your dependencies are included in
Central.
I believe its worth removing. Having *all* artifacts in two repo managers is
always better then relying on single one.
On Thu, 30 Jan 2014 10:17:09 -0500
Bill Burke <bburke(a)redhat.com> wrote:
Resteasy 3.0.6 master pom (downloaded from maven central) has
repository.jboss.org as a repository and also has a jboss-web dependency
so I don't understand why Keycloak can't be pushed to maven central.
On 1/30/2014 9:30 AM, Karel Piwko wrote:
> Correct, Maven Central is even simpler to use. Works ootb, no mangling with
> settings.xml is required at all.
>
> I asked for pushing RESTEasy to Maven Central in Nov 2011, needed for
> EAP6/WFK2. There was the same clean up of pom.xml(s) back then.
>
> Performance wise, I have no idea. I'm not experiencing any difference at
> all. If you experience connection lags, you can always mirror Maven Central
> to a different repo, such as JBoss Nexus -
> http://maven.apache.org/guides/mini/guide-mirror-settings.html.
>
> Karel
>
> On Thu, 30 Jan 2014 08:45:20 -0500 (EST)
> Stian Thorgersen <stian(a)redhat.com> wrote:
>
>> Hosting on Maven Central means that folks can use Keycloak artifaces
>> without having to add JBoss Nexus to their poms. So IMO it makes it
>> slightly simpler to add Keycloak deps.
>>
>> RestEasy is on Maven Central
>> (http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
>>
>> ----- Original Message -----
>>> From: "Bill Burke" <bburke(a)redhat.com>
>>> To: keycloak-dev(a)lists.jboss.org
>>> Sent: Thursday, 30 January, 2014 1:37:47 PM
>>> Subject: Re: [keycloak-dev] Keycloak artifacts not in Maven Central
>>>
>>>
>>>
>>> On 1/30/2014 8:13 AM, Karel Piwko wrote:
>>>> I did some checks and there is some work needed:
>>>>
>>>> 1/ According to Maven Central rules, there should not be any
<repository>
>>>> elements in pom.xml files
>>>
>>>
>>>> 2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
>>>> available no Maven Central
>>>>
>>>> So, following steps are needed:
>>>>
>>>> * figure out whether jbossweb dependency could be replaced by something
>>>> else,
>>>> if not - it has to undergo same checks as keycloak and be synced to
>>>> Maven
>>>> Central or, which I prefer, to release it relocated to org.keycloak
>>>> groupId.
>>>> Given that 7.0.17.Final has do external dependencies at all -
>>>> seems much easier then trying to convince sonatype to pick a single
>>>> version
>>>> of jbossweb tree
>>>> * remove all <repositories> from pom.xml files
>>>>
>>>
>>> Would hosting at Maven Central require developers to configure their
>>> settings.xml, or can the build still run OOTB? A build running OOTB is
>>> more important than hosting at Maven Central.
>>>
>>> Also, what is the performance of Maven Central compared to
>>> repository.jboss.org? I've often had slow as balls connections to
Maven
>>> Central and never any problems with repository.jboss.org. Finally,
>>> nobody has ever complained that Resteasy is not at Maven central.
>>> People have no problems using repository.jboss.org so I don't see what
>>> the big deal is.
>>>
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
10:03 a.m.
Bill, I'm researching what happened that not all AS7 artifacts are synced to
Maven Central, as this not a problem of Keycloak nor Resteasy.
Once solved, I'll send a PR to remove <repository> elements from keycloak
and ask Sonatype guys to sync it to Central.
On Thu, 30 Jan 2014 10:17:09 -0500
Bill Burke <bburke(a)redhat.com> wrote:
Resteasy 3.0.6 master pom (downloaded from maven central) has
repository.jboss.org as a repository and also has a jboss-web dependency
so I don't understand why Keycloak can't be pushed to maven central.
On 1/30/2014 9:30 AM, Karel Piwko wrote:
> Correct, Maven Central is even simpler to use. Works ootb, no mangling with
> settings.xml is required at all.
>
> I asked for pushing RESTEasy to Maven Central in Nov 2011, needed for
> EAP6/WFK2. There was the same clean up of pom.xml(s) back then.
>
> Performance wise, I have no idea. I'm not experiencing any difference at
> all. If you experience connection lags, you can always mirror Maven Central
> to a different repo, such as JBoss Nexus -
> http://maven.apache.org/guides/mini/guide-mirror-settings.html.
>
> Karel
>
> On Thu, 30 Jan 2014 08:45:20 -0500 (EST)
> Stian Thorgersen <stian(a)redhat.com> wrote:
>
>> Hosting on Maven Central means that folks can use Keycloak artifaces
>> without having to add JBoss Nexus to their poms. So IMO it makes it
>> slightly simpler to add Keycloak deps.
>>
>> RestEasy is on Maven Central
>> (http://search.maven.org/#search%7Cga%7C1%7Cresteasy) ;)
>>
>> ----- Original Message -----
>>> From: "Bill Burke" <bburke(a)redhat.com>
>>> To: keycloak-dev(a)lists.jboss.org
>>> Sent: Thursday, 30 January, 2014 1:37:47 PM
>>> Subject: Re: [keycloak-dev] Keycloak artifacts not in Maven Central
>>>
>>>
>>>
>>> On 1/30/2014 8:13 AM, Karel Piwko wrote:
>>>> I did some checks and there is some work needed:
>>>>
>>>> 1/ According to Maven Central rules, there should not be any
<repository>
>>>> elements in pom.xml files
>>>
>>>
>>>> 2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is not
>>>> available no Maven Central
>>>>
>>>> So, following steps are needed:
>>>>
>>>> * figure out whether jbossweb dependency could be replaced by something
>>>> else,
>>>> if not - it has to undergo same checks as keycloak and be synced to
>>>> Maven
>>>> Central or, which I prefer, to release it relocated to org.keycloak
>>>> groupId.
>>>> Given that 7.0.17.Final has do external dependencies at all -
>>>> seems much easier then trying to convince sonatype to pick a single
>>>> version
>>>> of jbossweb tree
>>>> * remove all <repositories> from pom.xml files
>>>>
>>>
>>> Would hosting at Maven Central require developers to configure their
>>> settings.xml, or can the build still run OOTB? A build running OOTB is
>>> more important than hosting at Maven Central.
>>>
>>> Also, what is the performance of Maven Central compared to
>>> repository.jboss.org? I've often had slow as balls connections to
Maven
>>> Central and never any problems with repository.jboss.org. Finally,
>>> nobody has ever complained that Resteasy is not at Maven central.
>>> People have no problems using repository.jboss.org so I don't see what
>>> the big deal is.
>>>
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
9:21 a.m.
On 01/30/2014 02:13 PM, Karel Piwko wrote:
I did some checks and there is some work needed:
1/ According to Maven Central rules, there should not be any <repository>
elements in pom.xml files
This is the rule that no one obeys on our side. In the end it is not
practical. What happens is that one of your transient deps has
<repository> element and you inherit it - you just have no clue from where.
2/ When I removed them, org.jboss.web:jbossweb:jar:7.0.17.Final is
not
available no Maven Central
So, following steps are needed:
* figure out whether jbossweb dependency could be replaced by something else,
if not - it has to undergo same checks as keycloak and be synced to Maven
Central or, which I prefer, to release it relocated to org.keycloak groupId.
Given that 7.0.17.Final has do external dependencies at all -
seems much easier then trying to convince sonatype to pick a single version
of jbossweb tree
* remove all <repositories> from pom.xml files
Then, 1.0-alpha-2 and further releases can be synced to Maven Central. Sonatype
might apply more rules but project looks in good shape Maven-wise IMO.
Karel
On Thu, 30 Jan 2014 05:22:07 -0500 (EST)
Stian Thorgersen <stian(a)redhat.com> wrote:
> That'd be great
>
> ----- Original Message -----
>> From: "Karel Piwko" <kpiwko(a)redhat.com>
>> To: keycloak-dev(a)lists.jboss.org
>> Sent: Thursday, 30 January, 2014 8:53:45 AM
>> Subject: [keycloak-dev] Keycloak artifacts not in Maven Central
>>
>> Hi,
>>
>> I've noticed that Keycloak Maven artifacts are not synced to Maven Central,
>> they are only on JBoss Nexus. Do you plan to sync them to Central?
>>
>> Let me know if so, I can help with that.
>>
>> Karel
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bolesław Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead
3727
days inactive
3732
days old
11 comments
4 participants
participants (4)
-
Bill Burke -
Bolesław Dawidowicz -
Karel Piwko -
Stian Thorgersen