accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4325) Bring Yetus Accumulo personality into our codebase
Date Fri, 03 Jun 2016 19:07:59 GMT


Josh Elser commented on ACCUMULO-4325:

bq. If we do create a devtools area, we should consolidate the Eclipse formatter files,,
and any other dev tools scattered around in our code, so at least it's all together, and clearly
separate from the project itself.


bq. I didn't realize it was coupled to specific branches.

Yeah, my original point about how we don't want to do JDK7 builds on master from the description.

bq. I agree a separate repository is silly. I'd almost prefer using a separate branch for
this sort of stuff, but I know that's not ideal either. We do have precedent with the
script (which I'm not a fan of being in our release either).

That's reasonable for precommits here (for automating it with ASF jenkins, we can easily pull
the personality out of another branch before running Yetus), but definitely not ideal for
the script (maybe we can do away with it eventually?).

> Bring Yetus Accumulo personality into our codebase
> --------------------------------------------------
>                 Key: ACCUMULO-4325
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>          Components: build
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.6, 1.7.3, 1.8.1
> I had put the "personality" (configuration for a project) for Accumulo into Yetus, but
it seems like we might be better served adding it directly to our project so we have better
control over it (e.g. no more jdk7 on master).

This message was sent by Atlassian JIRA

View raw message