Re: Work on Release 2.6: Maven Archetype and Tutorial Examples

Naveen, would you like commit rights?


> I'd also prefer the word "prevalentObject" (& "Prevalent Object") in the
> JavaDocs/manual/source code because "prevalentSystem" doesn't seem as
> specific to me.

I disagree. The least specific you can be in an OO context is to call
something an Object.


> I'd like the manual to occupy as few words as possible and be entirely after
> the "What is Prevayler?" paragraph on the Prevayler home page itself
> (Heading logo -> What is Prevayler? -> Code examples & guide -> Links).

Seems interesting.


> I'd
> like the manual's code examples to not go beyond a simple class with a
> boolean.

Too simple. It might seem you have to do that for every instance you
change in your system. It doesn demo the need to query from within the
transaction (what used to be called the baptism problem).


> Also I think there should be a straight .jar download for people who don't
> use Maven.

Agreed 100%.


> The javadocs should only show the public API, not any internal classes, in
> my opinion.

Agreed.

Klaus

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org