I don't have an immediate solution, but I hope one will emerge, at least for released versions of Spring 3.2.x. I'm afraid I can't say more presently.
Meanwhile, you (and anyone else with similar concerns) may care to make your views known to the Spring community. I raised a JIRA () last year to prompt discussion and a recent forum thread () has been discussing this topic and mentions another JIRA ().
On 27 Sep 2012, at 08:48, Charles Vuijst wrote:
To prepare for the transfer to Java 7, I’ve been reading about the related issues on different forums. I noticed the following:
It says that Virgo 3.6.0 supports Java 7, but for the known performance problem with the Spring framework, an additional upgrade is proposed to Spring 3.2 when that one becomes available.
That “…“ Spring 3.2 and beyond will not ship by default with OSGi metadata anymore ”…”
I opened a couple of jars, and indeed, the Manifest.MF files are rather empty.
Anyone has more info if this is either going to be fixed by SpringSource or if some alternative will come up?
virgo-dev mailing listvirgo-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/virgo-dev