On Tue, Nov 27, 2012 at 12:57 AM, Paul Merlin <[email protected]> wrote: > org.qi4j.extension.cache-ehcache(false) -> beta, none, some > IMO this one should be in 2.0 as library/cache is.
Agree, but the whole cache extension isn't documented at all, which is a major flaw. I will try to put love into the docs. > org.qi4j.extension.entitystore-gae(false) -> beta, none, none > Interesting, I don't have its use. WDYT? Leave out for now. > org.qi4j.library.neo4j(false) -> beta, good, some > org.qi4j.extension.entitystore-neo4j(false) -> beta, none, some > Theses one use outdated Neo4j and don't work with new versions without > changes. > Need some love before being releasable. Agree. Problem is that Neo Technology themselves wrote this. > org.qi4j.extension.entitystore-voldemort(false) -> beta, none, some > What about this one? Leave out for now. > org.qi4j.extension.indexing-solr(brief) -> early, brief, none > This one do not provide an Index/Query service but only Index + native > solr queries. > In other words we can not use the Query API with it. Keep it in. It will never be used for Query API as the underlying language will not be able to support it. > org.qi4j.library.cxf(false) -> beta, none, some > Don't know this one, what about it? Likely only work against an old CXF version, so leave it out. It is intended to allow for auto wiring of services into WS endpoints with value composites as arguments and return values. > org.qi4j.library.eventsourcing(false) -> beta, none, some > org.qi4j.library.eventsourcing-jdbm(false) -> beta, none, some > org.qi4j.library.eventsourcing-rest(false) -> beta, none, some > We decided to postpone the native EventStore support in Qi4j. > Shall we release theses libraries with 2.0? I don't know. > org.qi4j.library.scripting(false) -> beta, none, some > org.qi4j.library.lang-beanshell(false) -> beta, none, some > org.qi4j.library.lang-groovy(false) -> beta, none, some > org.qi4j.library.lang-javascript(false) -> beta, none, some > org.qi4j.library.lang-jruby(false) -> beta, none, some > org.qi4j.library.lang-scala(false) -> beta, none, some > Do we put effort on documentation and review of theses ones for 2.0 ? Leave out for now. It is additive functionality, and I think there are no problems of adding them back later. > org.qi4j.library.metrics(false) -> early, none, none > I'm very interested on this one but had no time to get a detailled look. > Niclas? There should be a corresponding extension for metrics (yammer), which I think UnitOfWork will hook into, and Usecases drives the metrics. Don't recall the details, but I suspect that it can be left out (=disabled in Core), or we can keep it in as a non-documented feature. > org.qi4j.library.spring(false) -> beta, none, some > I have to interest in this one but I understand it's important. > WDYT? Leave it out for now, and we can fanfare that as a new big feature in 2.1 or 2.2 > org.qi4j.library.struts2-codebehind(false) -> beta, none, some > org.qi4j.library.struts2-convention(false) -> beta, none, some > org.qi4j.library.struts2-plugin(false) -> beta, none, some > I have no use of this one, do you? Leave it out for the same reason. What happened to "Play" ? Cheers -- Niclas Hedhman, Software Developer 河南南路555弄15号1901室。 http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
