2.x release notes
2.1.1.RELEASE
Across Core
- 
minor performance improvements
 - 
@PostRefreshnow supports method arguments, behaving as an equivalent of@Autowiredbut after the Across context has bootstrapped- 
it is also possible to indicate that dependencies are not required, if dependencies are not met, the method will not be executed
 - 
@PostRefreshmethods can be called more than once if a parentApplicationContextrefreshes 
 - 
 
2.1.0.RELEASE
Across Core
- 
bootstrap locking changes
- 
the bootstrap lock is now taken and released per installer instead of once for the entire bootstrap phase
 - 
lock owner id is prefixed with both the
AcrossContext#displayNameand the hostname of the server 
 - 
 - 
event handlers are now executed in module bootstrap order: event handlers from a previous module will have been executed when yours is called
- 
this removes an old limitation of event handling in Across
 
 - 
 
Across Web
- 
@AcrossApplicationhas adisplayNameattribute to configure the context display name- 
if empty, the property value of across.displayName will be considered instead
 
 - 
 - 
added
LocalizedTextResolverfor generic localization of text snippets- 
ViewElementBuilderContextalso implements text and message code resolving (see BootstrapUiModule documentation) 
 - 
 - 
the default Thymeleaf resolvers now support templates with *.html suffix
- 
.html extension is now preferred as text editors will automatically recognize the template as html
 - 
.thtml extension is still fully supported but support may be removed in a future major release
 
 - 
 
2.0.0.RELEASE
Upgrade to Spring Platform Athens, new major dependency versions:
- 
Spring framework 4.3.x
 - 
Spring Boot 1.4.x
 - 
Thymeleaf 3.x
 
Across Core
- 
@AcrossEventHandlerhas been deprecated, all beans are now automatically scanned for@Eventmethods - 
the
AcrossEventPublisherinterface has some MBassador specific methods removed- 
note that the backing implementation of the event bus might change in the future, applications should avoid using MBassdor specific features
 
 - 
 - 
development mode will register a default resources directory for dynamic modules
- 
this will be an existing src/main/resources folder relative to the working directory of the running application
 
 - 
 - 
@ConditionalOnDevelopmentModeadded to detect if development mode is active 
Across Test
- 
The spring-boot-test dependency is now part of across-test
 - 
Updated documentation to use the new
@SpringBootTestannotation 
Across Web
- 
ServletContextInitializerbeans in modules are now supported directly for customizing theServletContext- 
@ConditionalOnConfigurableServletContextand@ConditionalOnNotConfigurableServletContextadded to determine ifServletContextcan still be customized - 
favour the use of
FilterRegistrationBeanorServletRegistrationBeaninstead ofAcrossWebDynamicServletConfigurer, the latter is now deprecated and will be removed in a future release 
 - 
 - 
Spring Boot devtools are now supported - application context restart will be triggered by default if devtools is on the classpath
 - 
AcrossWebModule now ensures that all
HandlerMappingbeans from other modules are exposed - 
a path prefix @static and @resource is registered to link to static resources
 - 
Thymeleaf dialect extensions
- 
using prefixes directly in url expressions is now supported
 - 
addition of across:static and across:resource attributes for generating links to static resources
 
 - 
 - 
add infrastructure for defining custom request mapping conditions using
@CustomRequestMappingandCustomRequestCondition - 
partial rendering of a single
ViewElementis now also supported (see BootstrapUiModule documentation).