accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Medinets (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-935) Run/Assemble Accumulo from Maven outside the source tree
Date Wed, 05 Jun 2013 03:00:20 GMT


David Medinets updated ACCUMULO-935:

               Labels: documentaion  (was: build maven)
    Affects Version/s: 1.6.0
               Status: Patch Available  (was: Open)

Sorry for not committing this myself. Better to offer a patch than let it sit in my VM for
a few days.
> Run/Assemble Accumulo from Maven outside the source tree
> --------------------------------------------------------
>                 Key: ACCUMULO-935
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: dist
>    Affects Versions: 1.6.0
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>              Labels: documentaion
>             Fix For: 1.6.0
>         Attachments: ACCUMOLO-935_update_readme_with_DEV_ACCUMULO_HOME_info.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> Too much of Accumulo's build runs directly out of the project directories, including
some in directories designated as "src". Temporary files are sometimes created outside the
source directories during unit tests, and other issues. This has caused us to jump through
hoops to exclude these temporary files during version control, packaging, and assembly. Instead
of jumping through these hoops, we can make sure everything created by the build, including
running Accumulo directly out of one's workspace is all done from a Maven /target directory
or a user-specified external directory. This will simplify our svn:ignore and .gitignore configuration,
as well as make it easier to package and assemble only the pieces we want to include, rather
than include a bunch of exceptions in the Maven build configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message