[
https://issues.apache.org/jira/browse/AVRO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986626#action_12986626
]
Scott Carey commented on AVRO-716:
----------------------------------
That can be an issue. Generally it is not.
For example -- if you have (like me)
src/avro-716/trunk
src/avro-737/trunk
src/avro-perf/trunk
and are using all three at the same time, you might mix/match things. There
are a few solutions:
* build from the top level -- it only uses snapshots in your if the code
required is not in the 'reactor' of the build. Note, this may be less
reliable (buggy) for the avro-maven-plugin. I've seen it use the local repo
over the reactor for the plugin once or twice, but more inside of the m2eclipse
plugin than command line.
* use 'install' more regularly -- if your work is interleaved, this should work
fine.
* change your version locally with mvn versions:set to create distinct
artifacts.
I'll explore this a little more to see what parts of our build are sensitive to
the repo and what parts aren't. There are a couple places where we call
directly to a sub-project instead of the parent, which will trigger dependency
on the local repo over the reactor. The build will be a little slower if we
use the top level instead, but probably more stable.
> 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
>
>
> 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.
