Apologies for the delays in getting a new release ready. There were a
number of recurring issues reported by openid4java users, and I wanted
them addressed before packaging a new release. These are:
a) the number of dependencies
b) the (outdated) version of some of the dependencies, and conflicts in
newer deployments
c) deployment of endorsed libraries
The latest patches of last week allow us to address all of these:
- openid4java has its own XRDS parser now
- the XRI local resolver was factored out into its own class
- there's now a proxy XRI resolver as well
The LocalXRIResolver is the only piece that depends on the openxri
library. Thus, openid4java can be packaged and distributed in (at least)
two flavors:
1) a significantly lighter one (using the proxy XRI resolver)
2) another one with the LocalXRIResolver and the openxri and the rest of
the required dependencies
The downside is that the code in the latest changes is fresh, and hasn't
seen enough real-world testing.
What would everyone prefer at this time?
- A fairly stable release of, say, some weeks ago, or
- A new release as outlined above, or
- both options?
Thanks,
Johnny
(just joined) any movement on this?
On Jan 31, 3:50 pm, Johnny Bufu <johnny.b...@gmail.com> wrote:
> Hello everyone,
>
> Apologies for the delays in getting a newreleaseready. There were a
> number of recurring issues reported by openid4java users, and I wanted
> them addressed before packaging a newrelease. These are:
>
> a) the number of dependencies
> b) the (outdated) version of some of the dependencies, and conflicts in
> newer deployments
> c) deployment of endorsed libraries
>
> The latest patches of last week allow us to address all of these:
> - openid4java has its own XRDS parser now
> - the XRI local resolver was factored out into its own class
> - there's now a proxy XRI resolver as well
>
> The LocalXRIResolver is the only piece that depends on the openxri
> library. Thus, openid4java can be packaged and distributed in (at least)
> two flavors:
>
> 1) a significantly lighter one (using the proxy XRI resolver)
> 2) another one with the LocalXRIResolver and the openxri and the rest of
> the required dependencies
>
> The downside is that the code in the latest changes is fresh, and hasn't
> seen enough real-world testing.
>
> What would everyone prefer at this time?
> - A fairly stablereleaseof, say, some weeks ago, or
> - A newreleaseas outlined above, or