[
https://issues.apache.org/jira/browse/ACCUMULO-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858523#comment-13858523
]
Josh Elser commented on ACCUMULO-2100:
--------------------------------------
[~mjwall] and I were talking about the GAV for the archetype as well. I think
we both agreed that it would make more sense to have the archetype implement
its own versioning instead of trying to match what Accumulo does (as I
previously did).
So, for whatever versions of Accumulo we have as "active", we could make an
accumulo-instamo-archetype-X (where X is the Accumulo major version). A couple
of nice gains come from this:
1. As we update the archetype, users don't have to update the version string
they use
2. Users will automatically get the newest version of Accumulo in that major
release.
> instamo-archetype could use a little clean up
> ---------------------------------------------
>
> Key: ACCUMULO-2100
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2100
> Project: Accumulo
> Issue Type: Improvement
> Components: instamo-archetype
> Reporter: Michael Wall
> Assignee: Josh Elser
> Priority: Minor
>
> Some of the things I noticed
> - mvn test fails, because it took longer than 30 secs to startup the MAC on
> my linux box.
> - README needs to be updated, usage is incorrect
> - pom.xml doesn't hook exec:exec into any lifecycle so you have to call mvn
> compile exec:exec -Pwhatever
> - Could abstract out a MiniAccumuloClusterWrapper to handle the temp
> directory clean up and make the usage across the ShellExample,
> MapReduceExample and ExampleAccumuloUnitTest consistent. Would also make it
> easier to implement ACCUMULO-2097 and ACCUMULO-2098
> BTW, I am running this against the origin/1.5 branch, targeting an archetype
> that is compatible with Accumulo 1.5.0
> Patch coming for review
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
