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-618) Update trace pom to identify artifact as trace and not cloudtrace
Date Fri, 25 Jan 2013 02:39:12 GMT

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

Christopher Tubbs commented on ACCUMULO-618:
--------------------------------------------

Does this matter? We also now have "instamo", an unbranded module like cloudtrace. Should
we also brand that artifact as "accumulo-instamo" and cloudtrace as "accumulo-trace"?

All these are pretty trivial changes, but I can think of at least one benefit: searching in
Maven repositories indicates that the artifacts are associated with the Accumulo software
stack (vs. simply being produced by the Accumulo group, which is indicated by the groupId).
                
> Update trace pom to identify artifact as trace and not cloudtrace
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-618
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-618
>             Project: Accumulo
>          Issue Type: Task
>          Components: trace
>            Reporter: John Vines
>            Assignee: Christopher Tubbs
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> the trace/pom.xml identfies the artifact as cloudtrace, which is an old convention. We
should update this to be just trace.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message