Instead of repeating all of the goodies and release details again, I’ll simply refer you to take a look at my recent post.   However to save you some time, here are the important new links:

Coherence Incubator Project:
http://cohinc.java.net

Coherence Community Source Code:
https://github.com/coherence-community

Release Documentation:
http://coherence-community.github.com/coherence-incubator/11.0.0/

Downloads:
If you’re not using Apache Maven for dependency management, you can still download the signed artifacts manually, including the jars, javadoc and source from Maven Central (which is http://search.maven.org/) Simply search for: “coherence incubator“.

What about Coherence Incubator 10?
Over the next few days, weeks and months our plan is to retire Coherence Incubator 10.  During this time we will be encouraging everyone to move over to Coherence Incubator 11.   There are a lot of advantages to this (like being able to easily build it yourself).  

Importantly we’ve gone to great lengths to ensure that Coherence Incubator 11 is technically the same as Coherence Incubator 10 - if they aren’t that’s a defect – which we should be able to resolve.  Basically anyone that’s currently using Coherence Incubator 10 should be able to simply swap the jars (updating the versions of course) and carry on.  Of course there are a few differences, but this are scoped to where and how examples are run, together with new documentation.

As we’ve previously done with major releases,  the old site, documentation and downloads for Coherence Incubator 10 will still be available.  We’re not taking those away.   However all new work and defect fixes will only occur in Coherence Incubator 11+ (unless there’s some monumental pressure – and I mean monumental).

Enjoy!

eg: Working on my notebook 11″ screen is fine.  Working on a 24″ screen is slow.  Working on a 30″ screen – scrolling just doesn’t work.   Of course the caveat here is that I’ve got white-space highlighting and line numbers turned on.  If I turn these features off it works fine.  However, I need and use these features everyday – hence it’s no longer a solution.

I tried a bunch of releases, patches, hacks, work-arounds and searched the code base.  However  there comes a point in time that trying to resolve the problem is far more painful than switching IDEs.

So I’ve switched.  I switched to JetBrains IntelliJ 11 (and 12).   It wasn’t easy and wasn’t exactly fun (after nearly 10 years on Eclipse there’s a lot of short-cuts to remember), but it’s worth it in terms of productivity.  (While I could use the Eclipse key-mappings, I have no intention on going back so I’m gradually learning the native IntelliJ ones).

Luckily all of my favorite plugins are supported, especially JIndent that I which I use routinely across around six different projects.

So… So long Eclipse.  You were once a great platform.  Now you’re slow, large and cumbersome (compared to other platforms out there).

PS: Buying a personal license of IntelliJ is so worth it!

Note: I say “almost” complete simply because we’ve not yet made an official release from the source repositories, but as far as openness goes, the work is now done.

If you’ve been looking at or using the Oracle Coherence Incubator in the past, a lot of things are about to change organizationally.

1. All source code and documentation is now officially licensed under CDDL.

2. The entire project has been “Mavenized”.  ie: easy to build, release etc from source.

3. All source code and documentation is now publicly available on GitHub.  ie: easy to access for everyone.

4. The project is now officially hosted at java.net.  ie: it’s like Glassfish and other open-source Java projects.

5. The issue tracking system is also publicly available (also on java.net).

6. The project documentation is now part of the project source (as a maven site).

7. You can now officially contribute to the Incubator!  Instructions on “how” are in the project documentation

8. Releases will be available on http://maven.java.net (and Maven Central).  Snapshots are already available on http://maven.java.net.

While these are major structural changes to the project, the source packaging and classes remain the same.   ie:  Coherence Incubator 11 is simply Coherence Incubator 10, but cleaned up with a new home and licensing model.

Here are the important new links:

Coherence Incubator Project: http://cohinc.java.net

Coherence Community Source Code: https://github.com/coherence-community

Latest Documentation: http://coherence-community.github.com/coherence-incubator/11.0.1-SNAPSHOT/

What about Coherence Incubator 10?

Ultimately the plan is to retire Coherence Incubator 10 and encourage everyone to move over to Coherence Incubator 11.   There are a lot of advantages to this (like being able to easily build stuff yourself).

Technically they are the same (if they aren’t that’s a defect – which we can track openly!).  We’ve gone to great lengths to keep them in sync so that everyone that’s been using Coherence Incubator 10 should be able to simply swap the jars (updating the versions) and carry on.

Once we’ve made an official release of Coherence Incubator 11, we plan to retire Coherence Incubator 10.  The site and downloads will still be available.  We’re not taking that away.   However all new work and defect fixes will only occur in Coherence Incubator 11 (unless there’s some monumental pressure – and I mean monumental).

Currently Coherence Incubator 11 contains a rollup of all changes to Coherence Incubator 10.  ie: in terms of source code they are the same (or very close).

So if you’re using Coherence Incubator 10, take a look at Coherence Incubator 11.  Grab the snapshots from maven.java.net or build it yourself from GitHub.

What’s next?

There’s still a bit of documentation to move over from Coherence Incubator 10 site and into Coherence Incubator 11.  We’re hoping to have this completed in the next week or so.  After this we’ll start the process of making an official release.  Once this is complete, we’ll announce retirement plan for Coherence Incubator 10.

As you can guess by the time this has taken, this has been a massive effort.  While it may seem like it was a simple project restructuring  - eg: getting source, documentation ready, this has involved a tremendous amount of organizational and community consultation.  I’m happy to say we’re through this now.   I look forward to putting out some new releases with new functionality pretty soon.

Yesterday the JCP made the important step of posting the Early Draft specification and API for JSR107. See http://jcp.org/en/jsr/detail?id=107 for details.

While an enormous amount of progress was made last year and early this year (by many people – not so much me) the JSR was somewhat delayed while the legals were resolved, especially with respect to ensuring clean and clear IP for Java itself, the eventual JCache Providers and the community.   Thankfully this stage is complete and we can move forward.

Source Code
For those of you that don’t know, all of the artifact are hosted on GitHub at https://github.com/jsr107.

If you’d like to pick up builds, you can do so from the CloudBees continuous build infrastructure here: https://jsr107.ci.cloudbees.com

JSR 107 Resourcing
Now the the Early Draft is out, Greg Luck (Terracotta) and myself (now a co-spec lead) will be committing the majority of our time to get this finished, together with appropriate implementations and the Technology Compatibility Kit (TCK), should you wish to write your own implementation.   However these things don’t happen in isolation so it would be greatly appreciated if you can free up some time over the next few months to take a look.   Unfortunately if we fail to get feedback, we’ll be force to make stuff up and “move on”.   ie: We both want this JSR completed asap.

JCP 2.7 Process
The Early Draft Review has now started and it is scheduled to end on 22 November. During this process we’ll continue to work on answering questions, making required changes etc.  Once complete we’ll start the Public Draft (another 30 days of review) and during the last week, we’ll schedule an EC ballot.  Should everything go well we’ll complete the RI and TCK then seek final approval for the JSR.

For those of you attending the next Coherence SIG (in London), I’ll be there to give an update and talk about Coherence support.

Cheers

– Brian

After about an hour or so of searching/reading, I found the following forum details a related permissions problem:

https://discussions.apple.com/thread/3194835?start=0&tstart=0

For some reason the “root” user doesn’t have read/write permissions to the Libraries folder!  Very weird.

Looking forward to 10.7.2 to fix the remaining “niggles”.

However I’m now completely “sold” on the new scrolling (reversed like the iPhone/iPad).  :P.  That and the new Mail.app are nice. Really looking forward to 10.7.2 or what ever the version is that will resolve the erratic mouse pointer acceleration.

A quick summary of the upgrade.
1. Upgraded Macbook 5.1 (first uni-body aluminum macbook released) from 4GB to 8GB ram.
2. Installed new Crucial M4 256GB Solid State Drive.
3. Performed Clean Install of Lion (via USB stick) – takes about 1 hr (probably would have been less if it didn’t hang half way through)
4. Install everything and migrate from old 256DB SATA drive to new install.

Elements of Frustration.
1. Random Mouse Pointer Jumping / Acceleration.
It seems OSX Lion is plagued with these problems. Don’t underestimate how annoying these are.  Seriously, your Mouse Pointer will simply disappear and randomly jump around the screen real-estate.  If you have multiple screens you’ll have to look to find it!

So far there are no fixes.  If tried everything I’ve found.   (this is on a regular Mighty Mouse).

2. Performance is Poor.
Out of the box it’s remarkably slow. Well, it appears to be remarkably slow. While there are some beautiful GUI transitions between windows, applications loading, spaces etc, these chew a lot of CPU. Basically add one second at a minimum to all window opening/application loading interactions (on my machine anyway). Luckily there are some solutions.

Open a terminal and execute these commands:

defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool NO
defaults write com.apple.Mail DisableReplyAnimations -bool YES

These will disable the animations for windows (which use to be an option in Snow Leopard, but is now gone).

3. Auto Repeat (when holding down a key) Doesn’t Work.
Yup. Amazing, but here’s how to turn it on (again using a terminal)

defaults write -g ApplePressAndHoldEnabled -bool false

4. Eclipse Margin Warnings Aren’t Displayed
There is a defect in Eclipse (all versions I can tell) that prevents the compiler error/warnings some being displayed in the right-hand scroll-bar area. This is fixed by turning on the “hide scroll bar” option.

Apple > System Preferences > General > Show Scroll Bars: Select "When Scrolling" Option.

Any other option seems to break Eclipse. Trust me, without this fix you’ll be searching for compiler errors by scrolling through each document by hand (or having to click through the Errors Panel).

5. Adium crashes intermittently
Not a biggy, but Adium randomly seems to crash if you change networks.  Have you upgrade to the “beta” as all other versions are not supported on Lion.  Funny, seems like is a “beta” too

Bottom line: Unless you’re willing to invest some time ironing these things out, I avoid the upgrade. I’m certainly not upgrading my other Mac’s.  If I had time I’d probably roll back, but I’m determined to move forward.

On the Positive Side: There are some very nice features, like the new Mail.app which I’ve become addicted to pretty quickly.