Releases: sitemesh/sitemesh3
3.2.1
Removed automatic Filter initialization. Moved to separate dependency sitemesh-webfilter jar
Changed automatic Filter naming from configurableSiteMeshFilter to sitemesh
Fixed Spring Boot defaults to initialize to null if not set.
dependencies {
// ... other dependencies
runtimeOnly 'org.sitemesh:sitemesh-webfilter:3.1.1'
}
Full Changelog: 3.2.0...3.2.1
3.1.1
Removed automatic Filter initialization. Moved to separate dependency sitemesh-webfilter jar
Changed automatic Filter naming from configurableSiteMeshFilter to sitemesh
Fixed Spring Boot defaults to initialize to null if not set.
dependencies {
// ... other dependencies
runtimeOnly 'org.sitemesh:sitemesh-webfilter:3.1.1'
}
Full Changelog: 3.1.0...3.1.1
3.2.0
Automatically configured by default and customizable either via java config or /WEB-INF/sitemesh3.xml
Since 3.2.0-M2, decorators are now expected to be in the /WEB-INF/decorators folder by default. This is can be changed via config.
This version is for use with Java 17+, Jakarta 8+, Spring Boot 3.x. Use 3.1.0 if you looking for Servlet, Spring Boot 2.x
Full Changelog: 3.0.1...3.2.0
3.1.0
Automatically configured by default and customizable either via java config or /WEB-INF/sitemesh3.xml
Since 3.1.0-M2, decorators are now expected to be in the /WEB-INF/decorators folder by default. This is can be changed via config.
This version is for use with Java 1.8+, Servlet 3+, Spring Boot 2.x. Use 3.2.0 if you looking for Jakarta, Spring Boot 3.x
Full Changelog: 3.0.1...3.1.0
3.2.0-M2
Convention Over Configuration but Still Completely Configurable
NOTE: This release is breaking and not compatible with previous releases due to a configuration change. The key difference being that this version can now run without any configuration files. Since Site Mesh 3 has no dependencies on any other artifacts, all that needs to be done to get up and running is to drop the sitemesh-3.2.0-M2.jar into your web applications lib folder and SiteMesh3 will configure itself automatically.
The only breaking change is that decorators are now expected to be stored in the /WEB-INF/decorators folder. However, this can be changed back by either using the .setPrefix("") or using sitemesh3.xml as follows:
<sitemesh>
<decorator-prefix>/WEB-INF/layouts/</decorator-prefix>
</sitemesh>If you want to upgrade to this version without moving anything around, simply just set the prefix to an empty String.
e.g.:
<sitemesh>
<decorator-prefix></decorator-prefix>
</sitemesh>One other thing to mention to 3.2.0-M1 Spring Boot users, we changed application.yml configuration to now be
sitemesh:
decorator:
...instead of being under spring: .
We did this because in the future we may explore allowing users to use yaml instead of xml or java for configuring SiteMesh.
Although we feel comfortable with using this version in a production environment. We are using Milestone versioning because the final release may incorporate breaking configuration changes from this version. Please read all release notes before upgrading to future versions.
Full Changelog: 3.2.0-M1...3.2.0-M2
We welcome any feed back. Expect an official 3.2.0 release soon!
3.1.0-M2
Convention Over Configuration but Still Completely Configurable
NOTE: This release is breaking and not compatible with previous releases due to a configuration change. The key difference being that this version can now run without any configuration files. Since Site Mesh 3 has no dependencies on any other artifacts, all that needs to be done to get up and running is to drop the sitemesh-3.1.0-M2.jar into your web applications lib folder and SiteMesh3 will configure itself automatically.
The only breaking change is that decorators are now expected to be stored in the /WEB-INF/decorators folder. However, this can be changed back by either using the .setPrefix("") or using sitemesh3.xml as follows:
<sitemesh>
<decorator-prefix>/WEB-INF/layouts/</decorator-prefix>
</sitemesh>If you want to upgrade to this version without moving anything around, simply just set the prefix to an empty String.
e.g.:
<sitemesh>
<decorator-prefix></decorator-prefix>
</sitemesh>One other thing to mention to 3.1.0-M1 Spring Boot users, we changed application.yml configuration to now be
sitemesh:
decorator:
...instead of being under spring: .
We did this because in the future we may explore allowing users to use yaml instead of xml or java for configuring SiteMesh.
Although we feel comfortable with using this version in a production environment. We are using Milestone versioning because the final release may incorporate breaking configuration changes from this version. Please read all release notes before upgrading to future versions.
Full Changelog: 3.1.0-M1...3.1.0-M2
We welcome any feed back. Expect an official 3.1.0 release soon!
3.2.0-M1
This is the first JDK 17 / Jakarta Release
This release includes the Spring Boot Starter and Example App
Although we feel comfortable with using this version in a production environment. We are using Milestone versioning because the final release may incorporate breaking configuration changes from this version. Please read all release notes before upgrading to future versions.
Full Changelog: https://github.com/sitemesh/sitemesh3/commits/3.2.0-M1
3.1.0-M1
Although we feel comfortable with using this version in a production environment. We are using Milestone versioning because the final release may incorporate breaking configuration changes from this version. Please read all release notes before upgrading to future versions.
This release includes the Spring Boot Starter and Example App
Full Changelog: https://github.com/sitemesh/sitemesh3/commits/3.1.0-M1