On 03/22/2016 04:00 AM, Shawn McKinney wrote: >> >> On Mar 21, 2016, at 2:51 PM, Stefan Seelmann <[email protected]> wrote: >> >> >> PS: Possible mprovements: >> * Update dependencies (e.g. Wicket 6.19->6.22|7.2 or Spring 4.0.0->4.2.5) >> * Automate instructions from quickstart / ten-minute-guide, e.g. using >> Docker > > The upgrade to Wicket 7 requires some work as some of the interfaces have > changed. We have an open ticket, just need to find the time. The bump to > 6.22 is doable as is going to Spring 4.2.5.
Ok, cool. I think a general check for updated dependencies before a release e.g. with "mvn versions:display-dependency-updates" should be added to the release process. > I’ve been thinking about a how-to using containers but have my work cut out > for me before taking it there. The Penn State team have a > 'fortress-in-a-box’ w/ Ansible which I is another option to automate > deployment of fortress and a directory impl. To be honest I don’t have a > firm grasp of these two technologies which is why I’ve held back up to now. No problem. It's just a goodie. When I see those detailed manual instruction I just think they need to be automated. I'd love to help but don't have free cycles currently.
