Apache CI Qpid-JMS* jobs temporary locked to Maven 3.3

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Apache CI Qpid-JMS* jobs temporary locked to Maven 3.3

Keith Wall
All,

I temporarily locked the Qpid-JMS* jobs to Maven 3.3 to avoid the
Jenkins/Maven issue being discussed on the infra@ list (thread: Maven
3.5 and NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE").

Once the issue is resolved, I'll revert it to the Maven (latest).

cheers, Keith.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Apache CI Qpid-JMS* jobs temporary locked to Maven 3.3

Robbie Gemmell
Administrator
Thanks Keith. I'd noticed the issue thread but hadn't updated the
config as a fix was expected quickly and the jobs havent been running
much. As the fix wasnt in place quickly (though is available) it makes
sense to change the config for now. I've updated the Windows job again
to get it working, those nodes have their own options in the dropdown
so it was still failing.

Robbie

On 16 June 2017 at 09:23, Keith W <[hidden email]> wrote:

> All,
>
> I temporarily locked the Qpid-JMS* jobs to Maven 3.3 to avoid the
> Jenkins/Maven issue being discussed on the infra@ list (thread: Maven
> 3.5 and NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE").
>
> Once the issue is resolved, I'll revert it to the Maven (latest).
>
> cheers, Keith.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...