Future State Version?

[reyno...@gmail.com]

Is it safe to assume that the github fork is going to be the more recent / better maintained version? Also, is their a JIRA or some other issue tracker I could follow for the Github fork?

[James Green]

I hope to answer the first question shortly - have reminded those responsible at 10Gen to answer my queries. The GitHub project has it's own issues tab.

On 21 May 2013 12:32, <reyno...@gmail.com> wrote:

Is it safe to assume that the github fork is going to be the more recent / better maintained version? Also, is their a JIRA or some other issue tracker I could follow for the Github fork?

--
You received this message because you are subscribed to the Google Groups "Morphia" group.
To unsubscribe from this group and stop receiving emails from it, send an email to morphia+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[reyno...@gmail.com]

Thank you very much. I did run into some things noting that this was supposed to become part of the standard mongo driver. Great work, would love to contribute...

[reyno...@gmail.com]

For example... on the wiki it states that SLF4J integration is achieved via  SLF4JLoggerImplFactory, but in v. 1.2.3 the line required is:

MorphiaLoggerFactory.registerLogger( SLF4JLogrImplFactory.class );

What would you prefer I do? Fork and fix the wiki and submit a pull request on that?

[James Green]

The wiki being the one on Google Code?

One the issues I haven't had a chance to look at and really must is that of documentation. Now I am a great believer of documenting software where the code lays which means docblocks. Exposing these in the form of a proper website has already been rather more difficult than it ought to be. Thankfully others are working in this area - see asciidoc and surrounding projects.

--

[Russell Bateman]

Just having well maintained Javadoc inside the code and source code JARs for use in Eclipse solves it for me most of the time. The original Morphia doc was lean on meaningful Javadoc. Seems like someone (or someones) very familiar with Morphia for having used it might be turned loose on the source code and, without fear of offending Scott or James or anyone, might just flesh out the methods and classes he or she totally groks--all to good effect and in very short order. It's less likely we'll get good doc if we hesitate and wait for some quantum decision or moment to do it.

Just my two cents. I'd volunteer if I thought I had two good clues, but I'm not there yet.

[reyno...@gmail.com]

I meant the Github wiki. Some of the pages are slightly out of date. I just want to know how I can help. Javadoc in source is great for the people willing to go that far... code examples are the best, and good up front plain English documentation can mean the difference in industry standard vs. obscurity (think of all the googlefu ninjas out there). I just want to help.

[James Green]

Apparently the wiki was locked to collaborators only. It's now open - go ahead.

1.3 of morphia is the trunk with an intention to remove anything that was marked @Deprecated some time ago. I've also made the entity cache a pluggable implementation at runtime and added support for javax.persistence.Id, I hope others will follow.

[Kevin]

I might be able to help with more code examples.

Kevin