[
https://issues.apache.org/jira/browse/AVRO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983922#action_12983922
]
Scott Carey commented on AVRO-716:
----------------------------------
bq. perhaps we should create a lang/java/build.sh
Good idea. I might be able to avoid the subshell too (and thus, let '-e' work).
on POM versions:
The maven-release-plugin can be used to change the version in the poms during
release. I believe it would be something like
{code}
mvn -B release:update-versions -DautoVersionSubmodules=true
-DdevelopmentVersion=`cat ../../share/VERSION.txt`
{code}
To change the versions to 1.5.0. Or, without the -B command it will prompt for
the version interactively.
I'll look into what the maven-properties-plugin can do. That might be simpler
-- most of the maven tools assume that that the whole build is within maven.
And we're never realistically going to have the same build system across 5+
languages.
> 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
>
>
> 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.
