I remember that at some point the test suite required unlimited strength encryption and that somebody went over all the test cases to change that. Maybe you could search in the archives to check what were the reasons for that and if they are still applicable today. If they still are, then you need to change the test cases.
Andreas On Sun, Mar 31, 2013 at 5:53 PM, Ruchith Fernando <[email protected]> wrote: > Hi Andreas, > > Thanks for the fix. Apologies for not noticing this earlier. > I suppose it we can add a note about this in the documentation. > > Thanks, > Ruchith > > On Sat, Mar 30, 2013 at 5:14 PM, Andreas Veithen > <[email protected]> wrote: >> Since nobody else seems to care: >> >> These build failures were caused by recent tests added by Ruchith and >> that require a JRE configured with unlimited strength encryption. To >> avoid the problem, I changed the configuration of the Jenkins job to >> use a JRE that satisfies this requirement. Not sure if that is what is >> expected and if something in the documentation needs to be changed. >> >> Andreas >> >> On Wed, Mar 27, 2013 at 4:51 PM, Apache Jenkins Server >> <[email protected]> wrote: >>> See <https://builds.apache.org/job/Rampart/1446/> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > > > > -- > http://ruchith.org --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
