The next release and kenai moving

I’m finally going to do a release of retepTools and retepMicroKernel this weekend, mainly due to it being a 3 day weekend here in the UK.

However, this weekend are moving datacentres, as part of Oracle’s slow consumption of Sun.

So the plan is going to be:

  1. Friday – No updates on the site (see below)
  2. Saturday – prepare retepTools then release
  3. Sunday – prepare retepMicroKernel then release
  4. Monday – any remaining cleanup

This will leave me with the Monday to tidy up. With kenai moving, the release will be done against the bitbucket mercurial repositories as the kenai ones will be unavailable (see below). When kenai have completed their move then I’ll sync the kenai repositories so they are back in sync.

Then I’ll be able to concentrate on the next release which will be primarily to get the artifacts deployed within maven central.

Finally, here’s the notification of this weekends migration over at

We’re Moving!

Kenai is moving from our old home into new digs. As part of the transition, we need to move quite a bit of data, which presents us with some interesting challenges.

On Friday (April 30th) @07:00 UTC, will be placed into a VIRTUAL READ-ONLY transitional mode. What does this mean?

1. SCM systems will be down, and not accessible.
2. Bug-tracking systems will be down, and not accessible.
3. Instant Messaging (IM) will continue to function.
4. Mailing lists will continue to function, but no email will be archived during this time.
5. The main website will be up, but with the following caveats:
* Project creation will be disabled.
* Account creation will be disabled.
* Any modifications to data, made during this transitional period, will be lost when we finally cut over to the new site.

It’s worth repeating : The websites will be up, but any changes made during the transitional period WILL NOT CARRY THROUGH AFTER CUTTING OVER TO THE NEW SITE.

We realize that this has the potential to cause some confusion, so for the duration of the transitional period, the website will sport a clear warning banner on every page.

Thank you for your participation in and loyalty with

Our very best,
The Team

Kenai to migration update

Just a quick one but finally I’ve received an update about whats happening with the migration of over to I was wondering what was happening as there’s been nothing apparent for a while now, well at least this helps.

Hi Everyone,

We told you we would have an update in about a month and that time has come.
The plan of record has not changed. Work is on-going for migrating the domain over to the Kenai infrastructure and we will move the existing projects over to the domain as soon as we have everything in place.

The work will take a bit of time to complete, so please feel comfortable using Project Kenai while we work towards the final move to

If you have any questions please continue to send them to the kenai-admin<at> alias as always. We’ll do our best to answers them.

Best Regards,

The Project Kenai Team

Kenai – is it closing or is it staying?

Well this is a bit of a shock – first they were going to close so a lot of projects (including myself) started migrating away as we had a deadline of 20th April but a couple of hours ago I got an email saying everything’s changed. Now it appears that they are going to migrate to the kenai architecture so all projects are going to be migrated there rather than just deleted.

Now they could have told us this in the first place and have saved a lot of us the now wasted time of migrating everything away from kenai – effectively 1 1/2 weeks wasted in ensuring nothing is lost.

It’s not all wasted effort however.

As I use a distributed scm (Mercurial) I’ve now got a working online backup of the sources over at – thats working fine, so if this is true then that will stay. I have an offline backup of the repos which I automatically push to anyhow, so getting that job to push back out to bitbucket is easy. As a bonus you can even see commits on twitter.

Also the maven repositories are at sonatype – so there maven is now working better than it did at kenai (one of the only two things I had problems with on kenai).

The one big problem I had in migrating was the project. I had created two projects on as that appeared to have something closer to kenai (other than jira). However I soon found two major downsides to it.

  1. You must have a javaforge account to clone from mercurial – you can’t even browse source unless logged in
  2. Anyone who submits a changeset must also have a javaforge account

Now these problems are terrible. It effectively locks you in to them and removes the benefits of having a distributed scm – receive a changeset from someone and push it to there – they automatically refuse the changeset. Also why prevent someone access to the source if they are anonymous? I’ve since found references to that problem where people have given up on javaforge because you can’t to it. Not good.

So what now?

Well I’m going to plod on – I’ve got a few major issues to sort out with JAXB and XMPP to deal with, so I’m going to see what is said over the weekend after the surprise announcement. If this is true then I’m going to stay with kenai/ – lets hope this means keeping jira! As others have said in the forums, kenai is the best forge out there and the only one with true IDE support with NetBeans’s kenai module.

I’ll finish off (it’s 3:30 in the morning right now) with the email about this change of heart from Oracle:


In an effort to get information out to the Kenai community quickly, while trying to manage the integration of our two companies, I think we did a poor job at communicating our plans for to you. I would like to remedy that now. Our strategy is simple. We don’t believe it makes sense to continue investing in multiple hosted development sites that are basically doing the same thing. Our plan is to shut down and focus our efforts on as the hosted development community. We are in the process of migrating to the kenai technology. This means that any project currently hosted on will be able to continue as you are on We are still working out the technical details, but the goal is to make this migration as seamless as possible for the current projects. So in the meantime I suggest that you stay put on and let us work through the details and get back to you later this month.

Thanks for your feedback and patience.

Ted Farrell
Oracle Corporation

%d bloggers like this: