Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Hudson » 3.2.0 Milestone 1 is available for Testing
3.2.0 Milestone 1 is available for Testing [message #1356911] Thu, 15 May 2014 05:20 Go to next message
Duncan Mills is currently offline Duncan Mills
Messages: 35
Registered: August 2011
Member

This initial milestone release is primarily concerned with the upgrade of our Spring library usage to Spring 3. As a result we've had a rev a bunch of plugins as well. More information over in the Hudson Blog

Give it a whirl!

The Hudson Team
Re: 3.2.0 Milestone 1 is available for Testing [message #1357312 is a reply to message #1356911] Thu, 15 May 2014 09:14 Go to previous messageGo to next message
Lukasz Jader is currently offline Lukasz Jader
Messages: 30
Registered: October 2013
Member
Any hope to implement https://bugs.eclipse.org/bugs/show_bug.cgi?id=433488 as part of 3.2.0 ?
Re: 3.2.0 Milestone 1 is available for Testing [message #1358057 is a reply to message #1357312] Thu, 15 May 2014 16:28 Go to previous messageGo to next message
Winston Prakash is currently offline Winston Prakash
Messages: 385
Registered: August 2011
Location: Fremont, CA USA
Senior Member
Yes, we will try to. It is small change. But the issue is, we need to deeply analyze the security issues associated with it. In general by-passing authorization is not a good idea. Most probably we will not make unprotected action active by default. But any one who understand and accept the vulnerabilities need to opt-in via global configuration and be responsible for the potential risk on that instance of Hudson.



Winston Prakash
Eclipse Hudson team
Re: 3.2.0 Milestone 1 is available for Testing [message #1383934 is a reply to message #1358057] Tue, 27 May 2014 05:33 Go to previous message
Lukasz Jader is currently offline Lukasz Jader
Messages: 30
Registered: October 2013
Member
Quote:
Most probably we will not make unprotected action active by default. But any one who understand and accept the vulnerabilities need to opt-in via global configuration and be responsible for the potential risk on that instance of Hudson.


This sounds perfectly fine for me!
Previous Topic:git/subversion plugins enhancements
Next Topic:Problems with SVN credentials and password parameters after upgrade
Goto Forum:
  


Current Time: Tue Jul 22 03:40:11 EDT 2014

Powered by FUDForum. Page generated in 0.01827 seconds