[ 
https://issues.apache.org/jira/browse/OAK-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976540#comment-15976540
 ] 

angela edited comment on OAK-6101 at 4/25/17 9:02 AM:
------------------------------------------------------

h4. 1. Renaming of oak-commons-run to oak-run-commons
- module renaming : committed revision 1792042
- adjusting packages : committed revision 1792045

h4. 2. Renaming oak-auth-* to oak-authentication-*
- _wontfix_

h4. 3. Renaming oak-segment-tar to oak-store-segment
-[~mduerig], i would leave that to you and the segment team to decide whether 
that's feasible.-
wontfix, the ripple effect is too big

h4. 4. Merge oak-examples and oak-exercises into oak-getting-started (or 
similar)
- MOVED to OAK-6125



was (Author: anchela):
h4. 1. Renaming of oak-commons-run to oak-run-commons
- module renaming : committed revision 1792042
- adjusting packages : committed revision 1792045

h4. 2. Renaming oak-auth-* to oak-authentication-*
- _wontfix_

h4. 3. Renaming oak-segment-tar to oak-store-segment
-[~mduerig], i would leave that to you and the segment team to decide whether 
that's feasible.-
wontfix, the ripple effect is too big

h4. 4. Merge oak-examples and oak-exercises into oak-getting-started (or 
similar)
- TODO


> Consistent naming of oak modules
> --------------------------------
>
>                 Key: OAK-6101
>                 URL: https://issues.apache.org/jira/browse/OAK-6101
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: angela
>            Priority: Minor
>             Fix For: 1.7.0, 1.8
>
>
> quoting mail from [~mduerig] on oak-dev list:
> {quote}
> Apart from renaming oak-commons-run to oak-run-commons there is:
> 1) oak-authentication-* instead of oak-auth-* as this would be inline
> with oak-authorization-*.
> 2) Also it is not obvious that oak-segment-tar and oak-store-spi are
> related. From that POC oak-segment-tar should be something like
> oak-store-segment.
> 3) Further oak-example and oak-exercise: the former already has sub
> modules. Maybe we can rename it to oak-getting-started (or similar) and
> move oak-exercise into the renamed one.
> I'm actually reluctant about 1) and 2) as renaming established modules
> have quite a ripple effect. As with 3) we already have sub-modules in
> one place we should probably start a discussion of switching to a
> hierarchical module structure. To address 1) and 2) once the main
> modularisation effort stabilised.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to