I've added an issue to include 2.1, thanks Raymond. Perhaps the JDO
team will fix the issue before we get it done on our end, but either
way it will be good to have it there.
Feel free to add yourself as a watcher to this issue:
https://issuetracker.springsource.com/browse/BRITS-119
- Chris
On Jul 23, 2008, at 8:00 PM, Raymond Lai wrote:
But unfortunately, I'm also using JDO 2.1 annotations which is
available only
from JDO 2.1 API. So... no go. :-(
Thanks for your kind help anyway,
Raymond
cbeams wrote:
Raymond,
In the meantime, consider using the bundle we've packaged within the
SpringSource Enterprise Bundle Repository. That manifest should be
OK.
http://springsource.com/repository/app/bundle/version/detail?name=com.springsource.javax.jdo&version=2.0.0
- Chris
Chris Beams
Sr. Consultant, SpringSource
http://springsource.com
On Jul 23, 2008, at 4:37 PM, Raymond Lai wrote:
Hi there,
As per discussion on
http://www.nabble.com/Is-it-a-bug--Felix-cannot-parse-Bundle-ManifestVersion-having-trailing-spaces-td18613664.html#a18617865
While they had committed a fix to Felix, the people there suggests
it's also
the problem of the JDO2 API's jar file - more specifially, is this
line:
Bundle-ManifestVersion: 2
The trailing space after 2 was causing the problem that made JDO2
API cannot
be started on Apache Felix as an OSGi bundle.
Would the people working on the JDO spec fix this line?
TIA,
Raymond
--
View this message in context:
http://www.nabble.com/JDO2-API%27s-manifest-file-problem-with-Apache-Felix-tp18622812p18622812.html
Sent from the JDO - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/JDO2-API%27s-manifest-file-problem-with-Apache-Felix-tp18622812p18624618.html
Sent from the JDO - User mailing list archive at Nabble.com.
