Robbie Gemmell commented on PROTON-270:

I dont particularly mind the group id, as I think the artifact id is likely 
going to have to contain proton in order to differentiate the jar names from 
other projects (or parent projects), meaning either way works for the groupId.

My only real interest in this was that at some point we should end up with 
naming being somewhat consistent between releases and between artifacts. Thus 
far it seems like almost every release of proton-j has had different artifact 
names than the last, which makes it slightly harder for users to track new 
releases and clutters up search results (try searching for qpid artifacts and 
you also get some old proton results, then search for proton and you get a 
mixture of current and once or twice defunct proton artifacts names).
> Make artifactId for proton tests more descriptive
> -------------------------------------------------
>                 Key: PROTON-270
>                 URL: https://issues.apache.org/jira/browse/PROTON-270
>             Project: Qpid Proton
>          Issue Type: Improvement
>    Affects Versions: 0.4
>            Reporter: Keith Wall
>             Fix For: 0.5
> As raised by Robbie on the proton list 
> (http://mail-archives.apache.org/mod_mbox/qpid-proton/201303.mbox/%3ccafitrptig+tzl-tsvjop1qdtu74mxwzqxg_lwlysdnfv9sq...@mail.gmail.com%3e)
> Hi all,
> I just noticed the maven artifactId for the proton tests for 0.4:
> <dependency>
>   <groupId>org.apache.qpid</groupId>
>   <artifactId>tests</artifactId>
>   <version>0.4</version>
> </dependency>
> Can we add 'proton' to that Id for consistency with all the other
> artifacts, and perhaps also help clue users in on what they actually are?

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

Reply via email to