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] Updated: (AVRO-716) New Java build: integrate with parent build and remove cruft
Date Sun, 30 Jan 2011 01:31:43 GMT

     [ https://issues.apache.org/jira/browse/AVRO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Scott Carey updated AVRO-716:

    Attachment: AVRO-716.v4.patch

Updated patch and script.

Run the patch before the script.

./build.sh clean test dist

does not use the local repo to publish artifacts at any time.  Script includes deletion of
old build items and change in svn:ignore.

With a change like this, do we need to modify CHANGES.txt?  Or is the comment from the parent
AVRO-647 sufficient?  The most we can say is "Java: integrate AVRO-647 changes with top level

> New Java build: integrate with parent build and remove cruft
> ------------------------------------------------------------
>                 Key: AVRO-716
>                 URL: https://issues.apache.org/jira/browse/AVRO-716
>             Project: Avro
>          Issue Type: Task
>          Components: build, java
>            Reporter: Scott Carey
>            Assignee: Scott Carey
>            Priority: Blocker
>             Fix For: 1.5.0
>         Attachments: AVRO-716.v1.patch, AVRO-716.v2.patch, AVRO-716.v3.patch, AVRO-716.v4.patch,
> We have legacy ant and ivy items in lang/java that need to be removed or reduced.   
> 'ant clean' 'and compile' and 'ant test' can simply forward to maven, we might still
want to have ant drive interop tests, and it is useful to have ant around as a tool.
> Additionally, buildbot currently fails and build.sh from the top level does not properly
build Java.

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

View raw message