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

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

@Holger

What maven version are you using?

Try 'mvn install -DskipTests -U'  which will force an update of your local repo 
and do a full build and install of libraries to your local repo. 

If you still have problems, make sure your settings.xml (local maven 
configuration) is not directing you to a corporate maven repository that 
potentially is blocking certain libraries or failing to proxy others. 

@Doug
I will commit this patch.  There may subsequently be some trivial changes to 
move dangling folders or package.html files.  If there are, I'll have a second 
patch since those changes should be trivial to review alone.


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

Reply via email to