jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart" <christophe.lomb...@gmail.com>
Subject Re: Better Jira components
Date Wed, 08 Aug 2007 07:37:30 GMT
Why not for the jcr-mapping somerthing like :

jcr-mapping
  ocm
  nodetype-management
  annotation
  spring



On 8/8/07, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>
> Hi,
>
> I'd like to streamline the Jackrabbit components in Jira (currently
> core, xml, query, etc.) to better match the project structure in svn.
> This would help us better track changes per release artifact.
>
> See below for a proposed restructuring of the Jira components. In
> short this change would lessen the categorization metadata on
> jackrabbit-core issues but increase metadata on other components. If
> we want to keep the finer granularity, we could use an prefix
> mechanism like core:query, core:xml, etc.
>
> BR,
>
> Jukka Zitting
>
> ----
>
> contrib
>     contrib PMs
>
> jackrabbit-api
>     Jackrabbit API
>
> jackrabbit-classloader
>
> jackrabbit-core
>     clustering
>     config
>     core
>     locks
>     xml
>     xpath
>     namespace
>     nodetype
>     observation
>     query
>     security
>     sql
>     transactions
>     versioning
>
> jackrabbit-jca
>     jca
>
> jackrabbit-jcr-commons
>
> jackrabbit-jcr-rmi
>     rmi
>
> jackrabbit-jcr-server
>
> jackrabbit-jcr-servlet
>
> jackrabbit-jcr-tests
>     test
>     JCR TCK
>
> jackrabbit-site
>     docs
>     site
>
> jackrabbit-text-extractors
>     indexing
>
> jackrabbit-webapp
>     webapp
>
> jackrabbit-webdav
>     webdav
>
> There are also a few generic and not yet released components that I
> haven't yet figured how to best handle:
>
>     JCR 1.0.1
>     JCR 2.0
>     JCR API
>     jcr-mapping
>     jira
>     maven
>     SPI
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message