Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <21771363.68461295477085192.JavaMail.jira@thor>
Date: Wed, 19 Jan 2011 17:44:45 -0500 (EST)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Subject: [jira] Commented: (AVRO-737) Java: Improve correlation between
 packages and modules
In-Reply-To: <6597009.43531295383783544.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting commented on AVRO-737:
-----------------------------------

There shouldn't be a problem moving tool implementations to the tools module, since the tools module depends on every other module.  There could be issues if a Tool depends on a non-public API, that that would be a bug anyway, I think.

> 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.