I think you got the 403 due to it already being registered.
There should be two versions available 1.0-beta3 and 1.0-beta4-pre. Once we release
1.0.final it'll be tagged as 1.0. The 1.0-beta3 syntax should work as jQuery uses it
;)
----- Original Message -----
From: "Joshua Bellamy-Henn" <josh(a)psidox.com>
To: "Stian Thorgersen" <stian(a)redhat.com>
Cc: "Josh" <smysnk(a)gmail.com>, keycloak-user(a)lists.jboss.org
Sent: Wednesday, 30 July, 2014 9:13:21 PM
Subject: Re: [keycloak-user] Bower for keycloak.js
So I've tried to register this package for you guys using bower:
~/play/keycloak-js-bower master 14:08:22
$ bower register keycloak
git://github.com/keycloak/keycloak-js-bower.git
bower keycloak#* resolve git://
github.com/keycloak/keycloak-js-bower.git#*
bower keycloak#* checkout master
bower keycloak#* resolved git://
github.com/keycloak/keycloak-js-bower.git#923dccb251
[?] Registering a package will make it installable via the registry (
https://bower.herokuapp.com), continue? Yes
bower keycloak register git://
github.com/keycloak/keycloak-js-bower.git
bower EUNKNOWN Unknown error: 403
I am afraid this could be due to the version number possibly being in an
incorrect format.
On Mon, Jul 14, 2014 at 10:46 AM, Joshua Bellamy-Henn <josh(a)psidox.com>
wrote:
> I removed the "keycloak" package, the name should be open for
registration
> now.
>
> Still bit skeptical it will accept anything other than "x.x.x" notation
> for versioning but give it a try. :)
>
> - Josh
>
>
> On Mon, Jul 14, 2014 at 5:10 AM, Stian Thorgersen <stian(a)redhat.com>
> wrote:
>
>> Have you contacted the Bower guys to get this changed yet?
>>
>> By the way we're going to stick with the same versioning that we use for
>> Keycloak except we'll remove -final from the final release. So versions
>> would be:
>>
>> 1.0-beta4
>> 1.0-rc1
>> 1.0
>>
>> That should mean that versions such as ">=1.0" will work, and will
only
>> use stable versions, while if someone wants to use a beta or rc they can
>> explicitly specify the version.
>>
>> ----- Original Message -----
>> > From: "Josh" <smysnk(a)gmail.com>
>> > To: "Stian Thorgersen" <stian(a)redhat.com>
>> > Cc: keycloak-user(a)lists.jboss.org
>> > Sent: Thursday, 3 July, 2014 4:46:09 PM
>> > Subject: Re: [keycloak-user] Bower for keycloak.js
>> >
>> > I do think there is a problem using that version format, I think I
>> tried it
>> > originally and bower was having none of it. This could be because they
>> use
>> > version for auto upgrade purposes, where one can use a "~"
character to
>> > prefix the version to allow upgrades in version minors in the bower.json
>> > file.
>> >
>> > eg.
>> > "dependencies": {
>> > "keycloak": "~0.3.12"
>> > },
>> >
>> >
>> > I have to admit I've been pulled to the dark side a little bit, it do
>> enjoy
>> > npm / bower for doing javascript type build processes (sometimes a
>> > necessary evil). I was never a a fan of 'grunt' but found that
'gulp'
>> is
>> > much better. I have a hybrid build process in my java apps where I
>> > sometimes break out of maven to execute some gulp build processes.
>> >
>> > But I understand for project like keycloak 'npm / gulp' adds a lot
of
>> > complexity to build process and is not desirable.
>> >
>> > I'll talk to the bower guys to get keycloak switched over to your fork
>> :D
>> >
>> >
>> >
>> > On Thu, Jul 3, 2014 at 7:08 AM, Stian Thorgersen <stian(a)redhat.com>
>> wrote:
>> >
>> > > I've pulled in your stuff to
>>
https://github.com/keycloak/keycloak-js-bower
>> > >
>> > > I'd prefer the versions to match with Keycloak versions
(1.0-beta-2,
>> > > 1.0-beta-3, 1.0-final). Do you know if that'll be a problem?
>> > >
>> > > Also, I'm going to add minification of keycloak.js to our Maven
build.
>> > > We'll need it there as well + we're mainly Java/Maven guys ;)
>> > >
>> > > ----- Original Message -----
>> > > > From: "Josh" <smysnk(a)gmail.com>
>> > > > To: "Stian Thorgersen" <stian(a)redhat.com>
>> > > > Cc: keycloak-user(a)lists.jboss.org
>> > > > Sent: Monday, 23 June, 2014 10:38:44 PM
>> > > > Subject: Re: [keycloak-user] Bower for keycloak.js
>> > > >
>> > > > Looks like it's a manual process at the moment to get
registry
>> moved to a
>> > > > different github endpont. Let me know when you have the project
>> setup
>> > > and
>> > > > I'll contact the bower guys.
>> > > >
>> > > > - Josh
>> > > >
>> > > >
>> > > > On Mon, Jun 23, 2014 at 12:56 PM, Josh <smysnk(a)gmail.com>
wrote:
>> > > >
>> > > > > You bet, I actually had the thought that it would be better
as
>> part of
>> > > the
>> > > > > release cycle. I'll have to figure out how to transfer
bower
>> > > repositories
>> > > > > because there was no login required to register a bower repo
and
>> > > currently
>> > > > > I have taken "keycloak" which would be optimal for
the project.
>> > > > >
>> > > > >
>> > > > > On Mon, Jun 23, 2014 at 2:40 AM, Stian Thorgersen <
>> stian(a)redhat.com>
>> > > > > wrote:
>> > > > >
>> > > > >> Hi Josh,
>> > > > >>
>> > > > >> That's great - thanks for contributing this. I would
like to
>> transfer
>> > > > >> this to
https://github.com/keycloak though, I hope your
happy
>> with
>> > > that.
>> > > > >>
>> > > > >> Thanks,
>> > > > >> Stian
>> > > > >>
>> > > > >> ----- Original Message -----
>> > > > >> > From: "Josh" <smysnk(a)gmail.com>
>> > > > >> > To: keycloak-user(a)lists.jboss.org
>> > > > >> > Sent: Friday, 20 June, 2014 6:30:02 PM
>> > > > >> > Subject: [keycloak-user] Bower for keycloak.js
>> > > > >> >
>> > > > >> > Hi guys,
>> > > > >> >
>> > > > >> > I have created a little github project to make
keycloak.js
>> > > available to
>> > > > >> bower
>> > > > >> > package manager .
>> > > > >> >
>> > > > >> > Project here:
>> > > > >> >
https://github.com/smysnk/keycloak-adapter-bower
>> > > > >> >
>> > > > >> > Usage:
>> > > > >> > $ bower install keycloak
>> > > > >> >
>> > > > >> > - Josh
>> > > > >> >
>> > > > >> >
>> > > > >> > _______________________________________________
>> > > > >> > keycloak-user mailing list
>> > > > >> > keycloak-user(a)lists.jboss.org
>> > > > >> >
https://lists.jboss.org/mailman/listinfo/keycloak-user
>> > > > >>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>