avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-737) Java: Improve correlation between packages and modules
Date Thu, 20 Jan 2011 00:15:46 GMT

    [ https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983946#action_12983946
] 

Scott Carey commented on AVRO-737:
----------------------------------


bq. There could be issues if a Tool depends on a non-public API, that that would be a bug
anyway, I think. 

Good point.  The only case this wouldn't be true would be if the tool was only for tests.
 But we could make a clone Tool interface for tests if we wanted to.   

I'll move them to the tools package/module.

> Java: Improve correlation between packages and modules
> ------------------------------------------------------
>
>                 Key: AVRO-737
>                 URL: https://issues.apache.org/jira/browse/AVRO-737
>             Project: Avro
>          Issue Type: Sub-task
>          Components: java
>            Reporter: Scott Carey
>            Assignee: Scott Carey
>             Fix For: 1.5.0
>
>         Attachments: AVRO-737.v1.patch
>
>
> Several packages have classes from multiple modules in the new layout.
> In general, we should avoid this.  Ideally, o.a.a.ipc would only exist in the avro-ipc.jar
for example.
> For 1.5.0, I'd like to move the easy stuff around to better correlate packages with modules.
> This will cause API changes we need to document.  Unfortunately, moving classes around
is not something you can do gradually.  Ideally these are isolated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message