You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2017/04/09 00:44:01 UTC
Jenkins and Maven 3.5.0
Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
make sense to switch to it there? I know in theory everything seems to work
with any version of Maven 3.x, but I'm also wondering if it's worth setting
up Jenkins like we did for Windows with multiple versions to catch any
strange build issues sooner rather than later.
--
Matt Sicker <bo...@gmail.com>
Re: Jenkins and Maven 3.5.0
Posted by Gary Gregory <ga...@gmail.com>.
Sure, why not? Let's eat our own Apache dog food. Fresh too!
Gary
On Apr 8, 2017 5:44 PM, "Matt Sicker" <bo...@gmail.com> wrote:
> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
> make sense to switch to it there? I know in theory everything seems to work
> with any version of Maven 3.x, but I'm also wondering if it's worth setting
> up Jenkins like we did for Windows with multiple versions to catch any
> strange build issues sooner rather than later.
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Jenkins and Maven 3.5.0
Posted by Apache <ra...@dslextreme.com>.
I typically will test the Log4J build during the maven release vote. That is the time to see if there are problems. I don't upgrade the maven version on the machine that performs the releases very often.
Ralph
> On Apr 9, 2017, at 8:20 AM, Gary Gregory <ga...@gmail.com> wrote:
>
> I was thinking of just using 3.5.0.
>
> Gary
>
>> On Apr 9, 2017 6:48 AM, "Apache" <ra...@dslextreme.com> wrote:
>> Why? There is no reason our build process has to support every maven release.
>>
>> Sent from my iPad
>>
>>> On Apr 8, 2017, at 5:44 PM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it make sense to switch to it there? I know in theory everything seems to work with any version of Maven 3.x, but I'm also wondering if it's worth setting up Jenkins like we did for Windows with multiple versions to catch any strange build issues sooner rather than later.
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
Re: Jenkins and Maven 3.5.0
Posted by Gary Gregory <ga...@gmail.com>.
I was thinking of just using 3.5.0.
Gary
On Apr 9, 2017 6:48 AM, "Apache" <ra...@dslextreme.com> wrote:
> Why? There is no reason our build process has to support every maven
> release.
>
> Sent from my iPad
>
> On Apr 8, 2017, at 5:44 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
> make sense to switch to it there? I know in theory everything seems to work
> with any version of Maven 3.x, but I'm also wondering if it's worth setting
> up Jenkins like we did for Windows with multiple versions to catch any
> strange build issues sooner rather than later.
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
Re: Jenkins and Maven 3.5.0
Posted by Apache <ra...@dslextreme.com>.
Why? There is no reason our build process has to support every maven release.
Sent from my iPad
> On Apr 8, 2017, at 5:44 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it make sense to switch to it there? I know in theory everything seems to work with any version of Maven 3.x, but I'm also wondering if it's worth setting up Jenkins like we did for Windows with multiple versions to catch any strange build issues sooner rather than later.
>
> --
> Matt Sicker <bo...@gmail.com>