3.7.2 Release

General Discussion Community Planning
1

Hi all,

Is there a proposed timescale on the 3.7.2 release?

We’re currently investigating moving our roster entries off the Openfire server and into an external store using the work done for http://issues.igniterealtime.org/browse/OF-418. Is there anything we can do to help get this work into trunk?

Thanks,

Michael

2

Howdy,

Guus wants to get this release out sooner than later To get this patch into trunk, he asked for a documentation patch as well. I have not looked into that aspect myself to know what exactly needs updating.

daryl

3

Thanks Daryl, that’s what I wanted to know - it isn’t immediately obvious what kind of documentation is needed. As far as I can see it’s a really similar idea to how the various AuthProvider mechanisms work, and they don’t seem to have any official documentation themselves.

Cheers

4

I was suggesting to add some kind of extention/modification of the pages as provided on http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/. Ideally, users should not have to rely on our source code alone to figure out how to make use of the new, pluggable RosterItem provider framework.

5

Thanks Guus, presumably this in in source control. I’m not sure I’m a commiter so I’ll send a patch if that’s easier. Which section would you want this in? A new one?

Cheers

6

It sure is! See http://fisheye.igniterealtime.org/browse/~br=trunk/openfire/trunk/documentation/ docs

I’d say either adapt db-integration-guide, or write a new page just like it - whatever works best for you.

7

Writing this as we speak, will ping it to you as a patch when I’m done.

Thanks,

Michael

8

Apologies for the delay, just got back from wedding and honeymoon. As promised, here is the documentation for the pluggable roster provider stuff. I tried to look through the forums at the various questions asked about the AuthProvider as it’s essentially the same approach (I didn’t write the RosterItemProvider though).

If you’re happy with it could you include the original patch for this issue? We’d really love to see this in as we’re starting to move our user relationship data to a graph database and want our Openfire installations to read from there.
OF-418-documentation.diff.zip (2391 Bytes)

9

Thanks, I have attached your patch to OF-418

10

Cheers Daryl, much appreciated. Is there anything else I can do to help at this point?

11

I tried to apply the code patch, but it failed (perhaps patch is older than current trunk or perhaps I am not clever enough to do so). I added you as a committer to svn, if you would like to do it yourself

12

The code patch isn’t mind I’m afraid but I’m happy to work on adding it to SVN. In fact, we have a story in our current sprint to do this so no excuses

Thanks for adding me, could you PM me the password I need to commit?

13

Its the same account you were using for XIFF commits

14

It’s been a while, any chance I can get a password reset? Is the username mikeycmccarthy or my full e-mail?

Thanks

15

I PM’d you about it

16

Thanks, committed. I haven’t quite got my development environment with IntelliJ up to scratch so if someone wouldn’t mind taking a look at this just to check it looks OK. I’ve put the code patch in as is.

17

Hi all - the last binary build doesn’t seem to have this code inside it. Is there a manual process to get the binary build done or should it happen nightly?

Thanks

18

Have a look at the build server: http://bamboo.igniterealtime.org/browse/OPENFIRE. It is lighting up like a christmas tree.

On first sight, I’d say that you introduced some @Override annotations to methods that implement in interface -which is not allowed in Java 5 (which Openfire reminds me of time and time again… been there, done that).

19

Ah, I did wonder about those - my IDE is moaning about them too but I applied to source patch as is. Fixed, apologies for that.