Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <12690058.184421295950389270.JavaMail.jira@thor>
Date: Tue, 25 Jan 2011 05:13:09 -0500 (EST)
From: =?utf-8?Q?Holger_Hoffst=C3=A4tte_=28JIRA=29?= <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: quoted-printable


    [ https://issues.apache.org/jira/browse/AVRO-737?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D129863=
13#action_12986313 ]=20

Holger Hoffst=C3=A4tte commented on AVRO-737:
----------------------------------------

The remaining problem is that the avro:test-jar is not yet found for assemb=
ling tools:

[ERROR] Failed to execute goal on project avro-tools: Could not resolve dep=
endencies for project org.apache.avro:avro-tools:jar:1.5.0-SNAPSHOT: Failur=
e to find org.apache.avro:avro:jar:tests:1.5.0-SNAPSHOT in http://tux:8080/=
nexus/content/groups/public was cached in the local repository, resolution =
will not be reattempted until the update interval of nexus has elapsed or u=
pdates are forced -> [Help 1]

There is no avro:avro-tests.jar created yet. Doing so manually will create =
the jar, but it will then not be seen or installed during the install phase=
 since it is not declared anywhere.


> 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, AVRO-737.v2.patch, AVRO-737.v3.pa=
tch, migrate_avro_packages.sh
>
>
> 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 pac=
kages with modules.
> This will cause API changes we need to document.  Unfortunately, moving c=
lasses around is not something you can do gradually.  Ideally these are iso=
lated.

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