[ 
https://issues.apache.org/jira/browse/ARTEMIS-1230?focusedWorklogId=226307&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-226307
 ]

ASF GitHub Bot logged work on ARTEMIS-1230:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Apr/19 20:06
            Start Date: 11/Apr/19 20:06
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on issue #2615: 
ARTEMIS-1230 Added artemis-bom
URL: https://github.com/apache/activemq-artemis/pull/2615#issuecomment-482291625
 
 
   So i think maybe it should be discussed on dev list to get the lay of the 
land. Im for it, but it needs to be discussed and have concensus as it is 
changing the way people are used to with the project quite a bit.
   
   Just to be clear i am against having a half and half approach. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 226307)
    Time Spent: 1h 20m  (was: 1h 10m)

> Create Maven Bill of Materials (BOM)
> ------------------------------------
>
>                 Key: ARTEMIS-1230
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1230
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Daniel Siviter
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> It's frustrating having to deal with dependency versions so the creation of a 
> Bill of Materials will assist with this.
> I'm currently battling with Wildfly Swarm 2017.6.0 overriding to 
> v1.1.0.wildfly017. To override the version of Artemis I have to have an entry 
> in my POM for every single dependency which is arduous.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to