[Hawkular-dev] maven stuff

Peter Palaga ppalaga at redhat.com
Thu Feb 26 08:11:23 EST 2015


On 02/25/2015 02:31 PM, Lukas Krejci wrote:
> On Tuesday, February 24, 2015 21:45:45 Peter Palaga wrote:
>> On 02/24/2015 08:01 PM, John Mazzitelli wrote:
>>>>> In addition, its getting annoying with having to rely on release
>>>>> versions of parent pom. I'm again waiting on release 8 because I
>>>>> added a new maven plugin to the parent.
>>>>
>>>> Please do not commit your own changes to the parent.
>>>> https://github.com/hawkular/hawkular-parent-pom#how-to-contribute
>>>
>>> Unless I misunderstand how this is supposed to work, this would mean
>>> I not only would have to wait for someone to peer review and merge my
>>> PR, but then I also have to wait for someone to take the time and
>>> push a release, and then wait for it to get into maven central
>>> because using it. And all I added was the xml maven plugin definition
>>> to the parent pom.
>>
>> No, you would not necessarily have to wait for all of that. It is only
>> public durable branches that should not depend on snapshots.
>
> Right there! We don't have public durable branches now, IMHO ;)

You joker :D -- P

>> Everybody
>> is free to depend on snapshots in his working copy and/or topic branches.
>>
>> If this fast dependency propagation is so important, we should setup
>> some kind of CI that will release an integrate timestamp-qualified
>> artifacts daily or even more often. With that, the builds would be
>> deterministic.
>>
>>> The reason why we had build problems this morning is because I
>>> screwed up the kettle build
>>
>> Sorry, I may have misinterpreted today's symptoms.
>> -- P
>>
>>> - and I was easily able to fix it by just
>>> committing stuff to the bus repo's master branch - travis and nexus
>>> picked up the snapshot builds easily and we were back running because
>>> everything else was picking up snapshots. I would have slit my wrists
>>> if I had to commit to the bus repo, wait for someone to merge it, up
>>> the version number, release it, then go to the kettle repo, up the
>>> version number of the bus artifacts, create PR/merge it, and release
>>> it. People would still be waiting for a good kettle build :)
>>> _______________________________________________ hawkular-dev mailing
>>> list hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>



More information about the hawkular-dev mailing list