Robbie Gemmell commented on PROTON-521:

Just to clarify as it probably isn't clear from my comment upon re-reading: I'm 
really not against changing it if there is a clear benefit, I just don't want 
to see us keep changing the names without having that good reason.

For example, I figured out the reason for 'qpid-proton' changing: it used to be 
the Java implementation and was the only maven artifact produced, but then the 
maven build was expanded to encompass running the tests and contrib artifacts 
and allow operation against proton-c (via proton-jni), and during that process 
'qpid-proton' was renamed 'proton-core' and then 'proton' (and subsequently 
'proton-j-impl', and now 'proton-j'). Some of those renames are easily 
justified, others not so much in my mind.

> Replace "proton-project" with "proton" in maven related build files
> -------------------------------------------------------------------
>                 Key: PROTON-521
>                 URL: https://issues.apache.org/jira/browse/PROTON-521
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.6
>            Reporter: Irina Boverman
>            Priority: Trivial
>             Fix For: 0.7
>         Attachments: replace-proton-project.txt
> This change makes it easier to build downstream products.

This message was sent by Atlassian JIRA

Reply via email to