Re: [VOTE] Turbine Webapp Archetype v7.0 Release Candidate
Jeffery Painter <[email protected]> Tue, 9 Dec 2025 06:09:10 -0500
| Newsgroups | gmane.comp.jakarta.turbine.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Georg, [X] +1 release it I was able to build and install the archetype without any issues. I then ran to generate the sample app and all seems to be working great. $mvn jetty:run and the demo popped right up. Now, I need to update my own apps to Turbine 7.0 :-) Thanks, Jeff On 11/28/25 08:54, Kallidis, Georg wrote: > Dear turbine devs, > > a new RC for the Turbine Webapp Archetype was prepared - > > Tag: turbine-webapp-7.0 > > Git repo: https://gitbox.apache.org/repos/asf/turbine-archetypes.git > > Artifacts: > > https://repository.apache.org/content/repositories/orgapacheturbine-1104/ > > > Changes include: > > - Support Turbine 7.0 and Torque 7.0 > > - Requires Java 17 > > - update fulcrum dependencies to match > > - update build plugin archetype-packaging to v.3.4.1 from 3.2.1, use > archetype-descriptor-1.2.0.xsd (from 1.0.0) > > - add profiles mariadb (now default for docker) and mysql > > - docker integration tested with podman > > - use the new logo instead of the feather in example app. > > - adding in pom default outputTimestamp (seconds for today) to be in allowed > time range for maven-remote-resources-plugin. > > - in example app persist changes to admin account after logout > > - Find more changes in changes.xml, e.g. use property connectionProperties, > evaluate db property in archetype pom.xml; setting dynamically profile > mariadb or mysql depending on selected archetype attribute 'db'. > > > I will update site.xml after the release, as I forgot it, and the site is > only a partial in the turbine web site, without any deprecated artifacts. > > > Please consider voting by replying with one option checked: > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > > > Thanks! > > Georg > > > > >