incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Connelly <>
Subject Re: JCR mapping release
Date Tue, 19 Sep 2006 08:27:22 GMT

[Repeating a posting I made recently on the Jackrabbit Dev's ocm 
thread.   The decision point appears to be at hand.]

Let me suggest that a *fresh* name for the "jcr mapping" component 
within Jackrabbit would help 1) create a bigger buzz, 2) bring in fresh 
contributors and 3) reduce confusion.

Here are a few names that I came up with.    To my knowledge, any one of 
these could be used without confusion.    But, *any* name shorter and 
snappier than "jcr-mapping" would be +1 with me.

   * Occam
   * Jacob
   * Snowshoe  (non-hibernating jackrabbit)
   * JackInPOX  (like JPOX, Java Persistent ObjectX)
   * Jacko

   -- Dan

Jukka Zitting wrote:

> hI,
> On 9/7/06, Dan Connelly <> wrote:
>> Any idea, at this point, what name you would use for this subproject in
>> Jackrabbit?
>> I have "graffito" in my dependent code now.   I would not want to change
>> this to "jackrabbit" as that would imply a dependency that does not
>> exist.   (Other JCRs are not excluded.)
> I would figure that the mapping too would end up as something like a
> "jcr-mapping" project within the "org.apache.jackrabbit" group. Note
> that the "Jackrabbit content repository" appears independently as a
> "jackrabbit-core" project within the same group, so having the mapping
> tool as a Jackrabbit subproject wouldn't imply a code dependency on
> the Jackrabbit core as they would both just share the JCR API
> dependency and the same groupId.
> BR,
> Jukka Zitting

Jukka Zitting wrote:

> Hi,
> To better prepare for a move to the Jackrabbit project, I'd like to
> propose making a release of the JCR mapping subproject. The code seems
> to be stable enough for a release and all the IP issues have already
> been resolved, so there should be no major remaining issues.
> Would someone like to step up as the release manager? It's a task that
> gets you pretty familiar with various policies and procedures of the
> ASF. I'll be happy to assist in any way I can.
> PS. I'd like to follow up with a release of also the full Graffito
> framework, but it's probably easier to do a more limited release
> first.
> BR,
> Jukka Zitting

View raw message