Stack 3.4.2 Released

Support and Announcements for the Tech Java Web Application Platform (setup, configuration, bugs, feedback).
New Member
Posts: 18
Joined: Wed Jan 05, 2011 10:28 am
Location: Kaysville, Utah, USA

Stack 3.4.2 Released

Postby campbellbd » Tue Feb 11, 2014 2:33 pm

The Java Stack team is pleased to announce the release of Stack 3.4.2. This release includes changes to better support Cloud Foundry deployment and was coordinated to occur along side the Cloud Foundry launch event on 2/12, see you there. I've heard there will be donuts.

Notable Changes
  • Made Cloud Foundry the default deployment option in Stack Starter.
  • Added field to Stack Starter for entering the portfolio name. While this is essential for Cloud Foundry deployments, it will also provide the ability for repository scanning tools to report on projects by portfolio.
  • Added JDK 1.8 as an option to Stack Starter for Java platform version. (JDK 1.7 remains the default.)
  • Upgraded Tomcat Maven plugin for Tomcat 7.0.47
  • Fixed tomcat deployment to mark *.sh files as executable. Previously this was breaking for paths containing spaces.
  • Tcat: STACK-4458 fix bug having to do with muli-part context paths (e.g., /foo/bar) -> thanks to Jared Betteridge for the Pull Request
  • Security-web: Fixed an XSS vulnerability in XSRF protection -> thanks to Clint Checketts for the Pull Request.
  • Security-web: added X-FRAME-OPTIONS via an optional, configurable filter.
  • Added better support for 3 character language codes with the Stack UrlLocaleResolver.
  • Added sesstionless HttpSession filters to prevent the HttpSession from being utilized in an application.
  • Spring Data JPA Repository Example in Stack Starter
  • DB Version Checker Spring Bean in Stack System. Allows you to require a specific version of the database migrations or else your application will fail to start.
  • STACK-4626 Allow the grunt task to be specified in the stack grunt maven plugin -> thanks to Clint Checketts for the pull request
    • grunt file should be at the root of your maven module.
    • node_modules directory will therefore be at the root of your maven module.
    • you might want to exclude the node_modules directory from vcs (especially SVN).
    • you can now specify the grunt task but it defaults to build so no changes are required.
    • you should make sure the generated output gets placed in the target directory as part of your grunt task definition.
  • Various additional bug fixes.
Now using DB Migrator version 4.1.4 which includes the following...
  • STACK-4679 Variable substitution in DB Migrator can now be fully controlled with Oracle compatible “set define” and “set escape” commands.
  • STACK-4314 Added a controllable logging mechanism to DB Migrator - Logback
For upgrade information please refer to our upgrade notes.

If you have any questions please contact a member of the team.


Return to “Java Web Project Support (Stack)”

Who is online

Users browsing this forum: No registered users