[
https://issues.apache.org/jira/browse/ACCUMULO-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859133#comment-13859133
]
Josh Elser commented on ACCUMULO-2100:
--------------------------------------
Because I don't think it *should* match the Accumulo versioning. Play along
with me for a little bit.
What we (at least, I) wanted to see from the Archetype is a simple way to spin
up Accumulo with some examples of code running against that version. Assuming
that we get (and stay) in a place where we match adhere to semantic versioning,
we really want archetypes against the major versions of Accumulo (right now 1.4
and 1.5, soon 1.6).
You'll also notice that the artifact was renamed to
accumulo-instamo-archetype-1.4. So, the accumulo-instamo-archetype-1.4 will
pull down and provide you the latest 1.4 variant of Accumulo. The versioning of
the archetype therefore also doesn't need to be arbitrarily tied to Accumulo
versions, nor does the user need to be cognizant of the versioning of each
artifact. Consider, how do handle updates to the example of the archetype that
don't change Accumulo version dependencies? We would have to introduce some new
versioning on top of the Accumulo version, and users would have to go and check
to find out that a new version was released.
I think this approach will:
# Be easier to use for users as they don't need to track Archetype versions
# Help keep us honest with upstream Accumulo versioning (eat our own dogfood)
Mike and I had talked about this over email before he made these tickets, so I
apologize for not having that here.
> 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)
