Closed GoogleCodeExporter closed 9 years ago
Can you try 0.99.1snapshot which is newer
Original comment by scotthernandez
on 15 Nov 2011 at 7:50
With 0.99.1-SNAPSHOT, I got the following exception (complete stack trace
attached). It may be related to version incompatibility between Mongo Java
Driver and Morphia version however I'm not sure. What do you think?
----------
Stack Trace:
Caused by: java.lang.NoClassDefFoundError: org/bson/BasicBSONEncoder
at com.google.code.morphia.Morphia.<init>(Morphia.java:46)
at com.google.code.morphia.Morphia.<init>(Morphia.java:42)
at play.modules.morphia.MorphiaPlugin.onConfigurationRead(MorphiaPlugin.java:231)
[...]
Caused by: java.lang.ClassNotFoundException: org.bson.BasicBSONEncoder
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
[...]
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 9 more
Original comment by ahmetalp...@gmail.com
on 15 Nov 2011 at 8:10
Attachments:
Yes, you need the 2.7.x driver
Original comment by scotthernandez
on 15 Nov 2011 at 8:14
Exactly the same exception persists on mongo-2.7.2.jar &
morphia-0.99.1-SNAPSHOT.jar.
Original comment by ahmetalp...@gmail.com
on 15 Nov 2011 at 8:25
This issue was closed by revision r1781.
Original comment by scotthernandez
on 16 Nov 2011 at 4:57
Thanks. However I checked out the code and then tried to mvn install and got
the following:
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.google.code.morphia:morphia:0.99.1-SNAPSHOT
(/Users/alp/morphia-read-only/morphia/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
com.google.code.morphia:morphia-parent:pom:1.2 in http://repo1.maven.org/maven2
was cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
When are you going to take next snapshot?
Original comment by ahmetalp...@gmail.com
on 16 Nov 2011 at 11:49
Original issue reported on code.google.com by
ahmetalp...@gmail.com
on 15 Nov 2011 at 7:46