What's new in Sculptor
Released versions of Sculptor:
- Version 3.1.x
- Version 3.0.x
- Version 2.1.x
- Version 2.0.x
- Version 1.9.x
- Version 1.8.x
- Version 1.7.x
- Version 1.6.x
- Version 1.5.x
- Version 1.4.x
- Version 1.3.x
- Version 1.2.x
- Version 1.1.x
- Version 1.0.x
Version 3.1.x
Version 3.1.0
Version 3.1.0 was released April 05, 2015.
Some highlights of the release:
- Upgrade to Eclipse Luna
- Upgrade to Xtext/Xtend 2.8
- Upgrade to Eclipse Tycho 0.22
- Upgrade to Spring 4.1
- Upgrade to Jave EE 6 (deployment descriptors and dependencies)
- Upgrade to JPA 2.0 by using Hibernate 4.2 (the last version of Hibernate which does not require JPA 2.1)
- Sculptor meta model based on Xcore now (instead of plain Ecore)
- Additional integration tests for Maven archetypes
- First version of Spring Data JPA cartridge
- New examples for Spring Boot, Pure EJB3 and Sculptor Cartridge for Spring Data JPA
API Breaking changes:
- Drop support for Java 6, Hibernate 3 and JPA 1
- Refactoring of
ServiceContext
into packageorg.sculptor.framework.context
- Refactoring of
JpaFlushEager
into packageorg.sculptor.framework.persistence
Version 3.0.x
Version 3.0.6
Version 3.0.6 was released September 09, 2014.
This release is a minor bug fix release which fixes a critical regression #148.
Version 3.0.5
Version 3.0.5 was released September 02, 2014.
This release contains:
- Upgrade to Xtext/Xtend 2.6.2
- Upgrade to Eclipse Tycho 0.21
- Migrated generators internal workflow from MWE2 script to Xtend program
- Refactoring of Builder and mongoDB cartridges into separate Maven projects within the new Maven module “sculptor-cartridges”
- Refactoring of generator library and generator test library Maven projects into the Maven module “sculptor-maven”
- Added support for returning a list of generator issues (in addition to the list of generated files) to SculptorGeneratorRunner
- Added parallel build support to Maven plugin (by removing usage of Java system properties in SculptorGeneratorRunner)
- Added support for handling multiple DbUnit XML files in DbUnit test base class
- Updated runtime dependencies to latest version of Jackson2 and XStream
Version 3.0.4
Version 3.0.4 was released June 02, 2014.
This release contains:
- Upgrade to Xtext/Xtend 2.6.0
- Refactoring of generator properties support into separate project
- Refactoring of Builder and mongoDB support into their own generator cartridges
- Added support for adding new generator properties in generator cartridges
- Added support for Sculptors extension mechnism in template test support
Version 3.0.3
Version 3.0.3 was released March 29, 2014.
This release contains:
- Support for generator properties which are common within a multi-module Maven project
- Refactoring of Maven plugins status file handling to improve file deletion on Windows
- Removal of obsolete code related to partial generation and CRUD UI generation
Version 3.0.2
Version 3.0.2 was released March 2, 2014.
This release contains:
- Upgrade to Xtext/Xtend 2.5.3
- Refactoring of Sculptor generator test code into separate Maven module
- Removal of Fornax OAW Maven plugin from build (Exec Maven plugin is used now)
Version 3.0.1
Version 3.0.1 was released January 18, 2014.
This release contains:
- Upgrade to Xtext/Xtend 2.5.0
- Support for mongoDB in Maven archetypes
- Support for Maven 3.1 logging in Maven plugin
- Support for Eclipse projects with Maven Integration (m2e) nature (resource folders in Java project have
excluded="*"
set in classpath properties) - Additional validations and quickfixes, e.g. for repositories in non-persistent events or reserved keywords used as ID
- Support for hyperlink navigation to imported model files
- Custom icon for Eclipse text editor and feature branding
- Additional EDA examples and missing MongoDB examples
Version 3.0.0
Version 3.0.0 was released November 29, 2013.
Some highlights of the release:
- Upgrade to Xtext/Xtend 2.4.3 and Eclipse Kepler
- Java package changed from
org.fornax.cartridges.sculptor
toorg.sculptor
- New Home Page: http://sculptorgenerator.org
- New Forum: https://groups.google.com/group/sculptorgenerator
- Version control changed from Subversion to Git
- Project hosting changed from Sourceforge to GitHub
- Website implemented via Jekyll Bootstrap
- Maven plugin available from Maven Central
- Eclipse plugin available from http://sculptorgenerator.org/updates
- Eclipse plugin build with Maven via Eclipse Tycho
- Release process based on Gitflow Maven plugin
- CI service via Travis CI
Version 2.1.x
Version 2.1.0
Version 2.1.0 was released January 21, 2012.
Some highlights of the release:
- JPA 2.0
- Convenient ways to query the database by defining queries in the model, see documentation in Advanced Tutorial
- Support for OpenJPA
- Validation based javax.validation api
- Builders with fluent interface for construction of domain objects, see documentation in Advanced Tutorial
- Major performance improvement in generation by suppressing invisible logging in beautifier
Version 2.0.x
Version 2.0.0
Version 2.0.0 was released March 13, 2011.
This release contains:
- RESTful Services
- Mixin composition with traits
- Spring Remoting
- Upgrade to Xtext 1.0 and Eclipse Helios
- Upgrade to Maven 3
- Upgrade to Spring 3.0
- Upgrade of versions for Google App Engine, Apache Camel, Spring Integration, Spring Web Flow, Drools, MongoDB, JBoss, Ehcache, Joda
- Change of logging API to SLF4J
- Removal of deprecated features
- Support DataTransferObject in CRUD GUI
- Persistent DomainEvent
Version 1.9.x
Version 1.9.0
Version 1.9.0 was released July 07, 2010.
This release contains:
- Support for MongoDB
- Support for Event-Driven Arcitecture (Publish/Subscribe, CQRS, Event Sourcing)
- New Home Page: http://sculptor.fornax-platform.org
- Generated Documentation
- More generated visualizations
- DSL language syntax
- GWT SmartClient improvements
- Support for Non persistent ValueObject in GUI
- Several improvements of generation of database DDL
- ToStringStyle
Version 1.8.x
Version 1.8.0
Version 1.8.0 was released February 16, 2010.
This release has the same functionality as previous 1.7.0, but internally it has been migrated to latest openArchitectureWare, which is now part of Eclipse. This means that the usability of the DSL editor is much better, e.g
- Better content assist (ctrl+space)
- Formatting (Pretty Printing) of model files (ctrl+shift+F)
- Templates (ctrl+space). This is a good complement to ordinary content assist. For example collection references.
Version 1.7.x
Version 1.7.0
Version 1.7.0 was released January 29, 2010.
This release contains:
- Support Google App Engine
- Support for additional JPA providers, EclipseLink, and DataNucleus
- CRUD GUI with GWT SmartClient
- JSF improvements
- Pure EJB3 target implementation (without Spring)
- Data Transfer Objects and Web Services with JAX-WS
- Pagination for queries
- Complex criteria support with internal DSL
- findByKey, built in query for the properties marked as key
- Hint for customization
Version 1.6.x
Version 1.6.0
Version 1.6.0 was released June 14, 2009.
This release contains:
- Support for JPA
- Support for Hibernate validator
- Spring annotations instead of XML
- JUnit 4 annotations
- Jetty and inmemory Hsqldb
- Spring Webflow 2
- Don’t generate gap classes by default
Version 1.5.x
Version 1.5.0
Version 1.5.0 was released February 1, 2009.
This release contains:
- New DSL for customization of the CRUD GUI
- New rich client dialect of the CRUD GUI
- Upgrade to oAW 4.3.1
- Port of the DDD Sample
Version 1.4.x
Version 1.4.1
Version 1.4.1 was released October 6, 2008.
The most important features of this release:
- JSF dialect of CRUD GUI.
- Possibility to split model.design into several files.
- Upgrade to oAW 4.3
- Support for Eclipse 3.4 Ganymede. Europa 3.3.2 is also supported.
Version 1.3.x
Version 1.3.1
Version 1.3.1 was released April 11, 2008.
This release is a minor bug fix release.
Version 1.3.0
Version 1.3.0 was released March 17, 2008.
The most important feature of 1.3 is a totally new metamodel for the CRUD GUI. In version 1.1 we implemented the CRUD GUI without a separate gui metamodel. The gui generation was using the business tier model. This was a good start, but the experience was that the templates and helper extensions became rather complicated. A special purpose gui metamodel simplified the templates and moved some of the logic to a transformation instead. This is important as we see the need for different dialects of the GUI. In the initial version we are using Spring WebFlow and JSP. We have also started a JSF dialect.
More is likely to come, such as rich client (RCP). Another motivation for the gui metamodel is the possibility to customize the GUI by using a separate DSL (in next release).
Version 1.2.x
Version 1.2.0
Version 1.2.0 was released December 9, 2007.
It is a technical upgrade of several core products such as Eclipse and openArchitectureWare.
Version 1.1.x
Version 1.1.1
Version 1.1.1 was released November 26, 2007.
This release is a minor bug fix release.
Version 1.1.0
Version 1.1.0 was released November 5, 2007.
This release includes a lot of useful features:
- A complete, but customizable, CRUD Gui is generated based on the domain model specified with the Sculptor DSL. The generated web application uses Spring Web Flow to achieve navigation of the associations in the domain model.
- Scaffold simplifies generation of CRUD operations and is perfect for prototyping together with the CRUD Gui.
- It is efficient to develop the domain model with a textual DSL, but for communication purposes it is useful to have a visual UML view. Sculptor automatically generates a class diagram of the domain model. Instantly updated documentation!
- Possibility to deploy without EJBs, i.e. to run in Tomcat.
Version 1.0.x
Version 1.0.1
Version 1.0.1 was released June 28, 2007.
This release is a minor bug fix release.
Version 1.0.0
Version 1.0.0 was released May 24, 2007.
The first final version of Sculptor has been released. The textual Domain Specific Language (DSL) and the design of theg enerated code are inspired by Domain-Driven Design. When using Sculptor you can focus on the business domain, instead of technical details. Sculptor uses openArchitectureWare to parse the DSL and generate high quality Java code and configuration. The generated code is based on well-known frameworks, such as Spring, Hibernate and Java EE.