accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4325) Bring Yetus Accumulo personality into our codebase
Date Fri, 03 Jun 2016 19:04:59 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314615#comment-15314615
] 

Christopher Tubbs commented on ACCUMULO-4325:
---------------------------------------------

I didn't realize it was coupled to specific branches. 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 build.sh script (which I'm not a fan of being in our
release either).

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

> Bring Yetus Accumulo personality into our codebase
> --------------------------------------------------
>
>                 Key: ACCUMULO-4325
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4325
>             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
(v6.3.4#6332)

Mime
View raw message