Hi,

The voting started but nobody except for me voted +1 so the release process
didn't finish. It would help if you could leave a vote on the voting email
at d...@aries.apache.org as well...

Cheers,

David

On 14 March 2017 at 09:17, Tom De Wolf <tom.dew...@aca-it.be> wrote:

> David,
>
> We have seen that you did the release of the esa-maven-plugin 1.0.2.
> However it is not yet available on https://mvnrepository.com/a
> rtifact/org.apache.aries/esa-maven-plugin, any idea when it can be
> expected there?
>
> Thanks,
>
> Tom
>
> Op ma 6 mrt. 2017 om 17:42 schreef Tom De Wolf <tom.dew...@aca-it.be>:
>
>> David,
>>
>> We tested our use cases and the current trunk version is working
>> perfectly. Thanks for releasing it this week and letting us know when it is
>> in maven central.
>>
>> Best regards,
>>
>> Tom
>>
>> Op ma 6 mrt. 2017 om 15:16 schreef David Bosschaert <
>> david.bosscha...@gmail.com>:
>>
>> Hi Tom,
>>
>> I'd be happy to cut a release sometime this week - could you please
>> double check that the current trunk version of the plugin works for you?
>>
>> Cheers,
>>
>> David
>>
>> On 6 March 2017 at 14:06, Tom De Wolf <tom.dew...@aca-it.be> wrote:
>>
>> David,
>>
>> Thanks for getting both pull requests merged into the esa-maven-plugin
>> trunk. What are the next steps to get a release of it available on the
>> central maven repository? When could we expect it so we can integrate it in
>> our application builds?
>>
>> Thx
>>
>> Tom
>>
>> Op do 2 mrt. 2017 om 16:47 schreef David Bosschaert <
>> david.bosscha...@gmail.com>:
>>
>> Hi Tom,
>>
>> I can take a look at it sometime soon.
>>
>> Cheers,
>>
>> David
>>
>> On 2 March 2017 at 15:26, Tom De Wolf <tom.dew...@aca-it.be> wrote:
>>
>> All,
>>
>> Who is maintainer of the esa-maven-plugin within the aries code base? We
>> have a few pull requests we would like to get accepted and delivered in a
>> new release:
>>
>> https://github.com/apache/aries/pull/69 for
>> https://issues.apache.org/jira/browse/ARIES-1490
>>
>> and
>> https://github.com/apache/aries/pull/63/ for https://issues.
>> apache.org/jira/browse/ARIES-1650
>>
>> As they both touch the same code it would be best to first merge pull
>> request 69, then we can adapt pull request 63 and get that reviewed and
>> merged.
>>
>> Any help would be much appreciated.
>>
>> Best regards,
>>
>> Tom De Wolf
>>
>>
>>
>>

Reply via email to