From f0b5bba6bbdc28d3dfa0dd6a539c8d89ddc1d639 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 6 Aug 2026 13:52:57 +0200 Subject: [PATCH 1/2] Rename the site documents ahead of converting them A pure rename, so that git records it and `git log --follow` and `git blame` still reach the history of each page after the conversion that follows. The content is still APT at this point and the site does not build between the two commits. --- .../multi-model.apt.vm => markdown/examples/multi-model.md.vm} | 0 .../src/site/{apt/index.apt => markdown/index.md} | 0 .../src/site/{apt/usage.apt.vm => markdown/usage.md.vm} | 0 .../{apt/location-tracking.apt => markdown/location-tracking.md} | 0 src/site/{apt/release-notes.apt => markdown/release-notes.md} | 0 5 files changed, 0 insertions(+), 0 deletions(-) rename modello-maven-plugin/src/site/{apt/examples/multi-model.apt.vm => markdown/examples/multi-model.md.vm} (100%) rename modello-maven-plugin/src/site/{apt/index.apt => markdown/index.md} (100%) rename modello-maven-plugin/src/site/{apt/usage.apt.vm => markdown/usage.md.vm} (100%) rename src/site/{apt/location-tracking.apt => markdown/location-tracking.md} (100%) rename src/site/{apt/release-notes.apt => markdown/release-notes.md} (100%) diff --git a/modello-maven-plugin/src/site/apt/examples/multi-model.apt.vm b/modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm similarity index 100% rename from modello-maven-plugin/src/site/apt/examples/multi-model.apt.vm rename to modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm diff --git a/modello-maven-plugin/src/site/apt/index.apt b/modello-maven-plugin/src/site/markdown/index.md similarity index 100% rename from modello-maven-plugin/src/site/apt/index.apt rename to modello-maven-plugin/src/site/markdown/index.md diff --git a/modello-maven-plugin/src/site/apt/usage.apt.vm b/modello-maven-plugin/src/site/markdown/usage.md.vm similarity index 100% rename from modello-maven-plugin/src/site/apt/usage.apt.vm rename to modello-maven-plugin/src/site/markdown/usage.md.vm diff --git a/src/site/apt/location-tracking.apt b/src/site/markdown/location-tracking.md similarity index 100% rename from src/site/apt/location-tracking.apt rename to src/site/markdown/location-tracking.md diff --git a/src/site/apt/release-notes.apt b/src/site/markdown/release-notes.md similarity index 100% rename from src/site/apt/release-notes.apt rename to src/site/markdown/release-notes.md From ac2abe6aae72266150bd4afad3d5ee29ef65d1d0 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 6 Aug 2026 13:52:57 +0200 Subject: [PATCH 2/2] Port the site documentation from APT to Markdown 5 page(s) converted with doxia-converter and then cleaned up by hand: - <<>> becomes backticks, <> becomes **bold**, {{{url}text}} becomes [text](url) - the ASF license header becomes a single block HTML comment - a page whose only Velocity reference was ${project.name} is now a plain .md with the title spelled out - a page that keeps a reference stays a .vm. Velocity reads ## as a line comment and would silently swallow every ATX heading below level one, so subsections use setext underlines and anything deeper is wrapped in #[[ ... ]]# - references APT rendered literally are escaped, so they do not resolve Verified by building the site before and after and comparing every generated page: the visible text and the link targets are unchanged apart from / becoming / and quotes in prose picking up the Markdown module's typographic substitution. --- .../site/markdown/examples/multi-model.md.vm | 21 +- .../src/site/markdown/index.md | 104 +-- .../src/site/markdown/usage.md.vm | 43 +- src/site/markdown/location-tracking.md | 83 +- src/site/markdown/release-notes.md | 731 +++++++----------- 5 files changed, 370 insertions(+), 612 deletions(-) diff --git a/modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm b/modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm index d034c5926..983910237 100644 --- a/modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm +++ b/modello-maven-plugin/src/site/markdown/examples/multi-model.md.vm @@ -1,20 +1,11 @@ - ------ - Example of multi-model configuration - ------ - Denis Cabasson - ------ - 10 August 2006 - ------ +# Processing Multiple Modello Models -Processing Multiple Modello Models +Configuring your pom.xml +------------------------ -* Configuring your pom.xml +You can use the following configuration in your `pom.xml` to have the Modello Plugin take two of your models into account (this configuration is taken from the maven-assembly-plugin which indeed uses two different models). - You can use the following configuration in your <<>> to have the Modello - Plugin take two of your models into account (this configuration is taken - from the maven-assembly-plugin which indeed uses two different models). - -+---+ +```xml [...] @@ -63,4 +54,4 @@ Processing Multiple Modello Models [...] -+---+ +``` diff --git a/modello-maven-plugin/src/site/markdown/index.md b/modello-maven-plugin/src/site/markdown/index.md index 62617a45b..b003d6eb1 100644 --- a/modello-maven-plugin/src/site/markdown/index.md +++ b/modello-maven-plugin/src/site/markdown/index.md @@ -1,85 +1,41 @@ - ------ - Introduction - ------ - Denis Cabasson - Hervé Boutemy - ------ - 1 January 2009 - ------ +# Modello Maven Plugin +This plugin makes use of the [Modello](https://codehaus-plexus.github.io/modello/) project. -Modello Maven Plugin +## Goals Overview - This plugin makes use of the {{{https://codehaus-plexus.github.io/modello/}Modello}} project. +- [modello:xsd](./xsd-mojo.html) Generates an XML Schema from the Modello model. +- [modello:xdoc](./xdoc-mojo.html) Generates standard documentation for the Modello model, in xdoc format. +- [modello:java](./java-mojo.html) Generates Java beans from the Modello model. +- [modello:xpp3-writer](./xpp3-writer-mojo.html) Generates an XML Pull Parser writer from the Modello model. +- [modello:xpp3-reader](./xpp3-reader-mojo.html) Generates an XML Pull Parser reader from the Modello model. +- [modello:xpp3-extended-reader](./xpp3-extended-reader-mojo.html) Generates an XML Pull Parser reader from the Modello model that records line/column number metadata and eventual source in the parsed model. +- [modello:xpp3-extended-writer](./xpp3-extended-writer-mojo.html) Generates an XML Pull Parser writer from the Modello model that writes line/column number and source info as comments on each line. +- [modello:dom4j-writer](./dom4j-writer-mojo.html) Generates a DOM4J writer from the Modello model. +- [modello:dom4j-reader](./dom4j-reader-mojo.html) Generates a DOM4J reader from the Modello model. +- [modello:stax-writer](./stax-writer-mojo.html) Generates a StAX writer from the Modello model. +- [modello:stax-reader](./stax-reader-mojo.html) Generates a StAX reader from the Modello model. +- [modello:jdom-writer](./jdom-writer-mojo.html) Generates a [jdom](http://www.jdom.org/) writer from the model that is capable of preserving element ordering and comments. +- [modello:jackson-writer](./jackson-writer-mojo.html) Generates a JSON writer based on Jackson Streaming APIs from the Modello model. +- [modello:jackson-reader](./jackson-reader-mojo.html) Generates a JSON reader based on Jackson Streaming APIs from the Modello model. +- [modello:jackson-extended-reader](./jackson-extended-reader-mojo.html) Generates a JSON reader based on Jackson Streaming APIs from the. Modello model that records line/column number metadata in the parsed model. +- [modello:snakeyaml-writer](./snakeyaml-writer-mojo.html) Generates a YAML writer based on SnakeYaml Streaming APIs from the Modello model. +- [modello:snakeyaml-reader](./snakeyaml-reader-mojo.html) Generates a YAML reader based on SnakeYaml Streaming APIs from the Modello model. +- [modello:snakeyaml-extended-reader](./snakeyaml-extended-reader-mojo.html) Generates a YAML reader based on SnakeYaml Streaming APIs from the. Modello model that records line/column number metadata in the parsed model. +- [modello:velocity](./velocity-mojo.html) Creates files from the model using Velocity templates. +- [modello:converters](./converters-mojo.html) Generates classes that can convert between different versions of the model. -* Goals Overview +## Usage - * {{{./xsd-mojo.html}modello:xsd}} Generates an XML Schema from the Modello model. +General instructions on how to use the Modello Plugin can be found on the [usage page](./usage.html). Some more specific use cases are described in the examples given below. - * {{{./xdoc-mojo.html}modello:xdoc}} Generates standard documentation for the Modello model, in xdoc format. +In case you still have questions regarding the plugin's usage, please have a look at the [FAQ](./faq.html) and feel free to contact the [user mailing list](./mailing-lists.html). The posts to the mailing list are archived and could already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching the [mail archive](./mailing-lists.html). - * {{{./java-mojo.html}modello:java}} Generates Java beans from the Modello model. +If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our [issue tracker](./issue-management.html). When creating a new issue, please provide a comprehensive description of your concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason, entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated. Of course, patches are welcome, too. Contributors can check out the project from our [source repository](./scm.html). - * {{{./xpp3-writer-mojo.html}modello:xpp3-writer}} Generates an XML Pull Parser writer from the Modello model. +## Examples - * {{{./xpp3-reader-mojo.html}modello:xpp3-reader}} Generates an XML Pull Parser reader from the Modello model. +To provide you with better understanding of some usages of the Modello Plugin, you can take a look at the following example: - * {{{./xpp3-extended-reader-mojo.html}modello:xpp3-extended-reader}} Generates an XML Pull Parser reader from the - Modello model that records line/column number metadata and eventual source in the parsed model. +- [Including multiple models](./examples/multi-model.html) - * {{{./xpp3-extended-writer-mojo.html}modello:xpp3-extended-writer}} Generates an XML Pull Parser writer from the - Modello model that writes line/column number and source info as comments on each line. - - * {{{./dom4j-writer-mojo.html}modello:dom4j-writer}} Generates a DOM4J writer from the Modello model. - - * {{{./dom4j-reader-mojo.html}modello:dom4j-reader}} Generates a DOM4J reader from the Modello model. - - * {{{./stax-writer-mojo.html}modello:stax-writer}} Generates a StAX writer from the Modello model. - - * {{{./stax-reader-mojo.html}modello:stax-reader}} Generates a StAX reader from the Modello model. - - * {{{./jdom-writer-mojo.html}modello:jdom-writer}} Generates a {{{http://www.jdom.org/}jdom}} writer from the model that is capable of preserving element ordering and comments. - - * {{{./jackson-writer-mojo.html}modello:jackson-writer}} Generates a JSON writer based on Jackson Streaming APIs from the Modello model. - - * {{{./jackson-reader-mojo.html}modello:jackson-reader}} Generates a JSON reader based on Jackson Streaming APIs from the Modello model. - - * {{{./jackson-extended-reader-mojo.html}modello:jackson-extended-reader}} Generates a JSON reader based on Jackson Streaming APIs from the. - Modello model that records line/column number metadata in the parsed model. - - * {{{./snakeyaml-writer-mojo.html}modello:snakeyaml-writer}} Generates a YAML writer based on SnakeYaml Streaming APIs from the Modello model. - - * {{{./snakeyaml-reader-mojo.html}modello:snakeyaml-reader}} Generates a YAML reader based on SnakeYaml Streaming APIs from the Modello model. - - * {{{./snakeyaml-extended-reader-mojo.html}modello:snakeyaml-extended-reader}} Generates a YAML reader based on SnakeYaml Streaming APIs from the. - Modello model that records line/column number metadata in the parsed model. - - * {{{./velocity-mojo.html}modello:velocity}} Creates files from the model using Velocity templates. - - * {{{./converters-mojo.html}modello:converters}} Generates classes that can convert between different versions of the model. - - [] - -* Usage - - General instructions on how to use the Modello Plugin can be found on the {{{./usage.html}usage page}}. Some more - specific use cases are described in the examples given below. - - In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel - free to contact the {{{./mailing-lists.html}user mailing list}}. The posts to the mailing list are archived and could - already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching - the {{{./mailing-lists.html}mail archive}}. - - If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our - {{{./issue-management.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your - concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason, - entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated. - Of course, patches are welcome, too. Contributors can check out the project from our - {{{./scm.html}source repository}}. - -* Examples - - To provide you with better understanding of some usages of the Modello Plugin, - you can take a look at the following example: - - * {{{./examples/multi-model.html}Including multiple models}} diff --git a/modello-maven-plugin/src/site/markdown/usage.md.vm b/modello-maven-plugin/src/site/markdown/usage.md.vm index 9fd6e2859..c80908c3d 100644 --- a/modello-maven-plugin/src/site/markdown/usage.md.vm +++ b/modello-maven-plugin/src/site/markdown/usage.md.vm @@ -1,22 +1,13 @@ - ------ - Usage - ------ - Denis Cabasson - ------ - 10 August 2006 - ------ +# Usage -Usage +This document is intended to provide instructions for using the modello-maven-plugin. - This document is intended to provide instructions for using the - modello-maven-plugin. +Typical configuration of the plugin in pom.xml +---------------------------------------------- -* Typical configuration of the plugin in pom.xml +You can use the following configuration in your `pom.xml` to invoke the Modello Plugin. - You can use the following configuration in your <<>> to invoke the Modello - Plugin. - -+---+ +```xml [...] @@ -65,22 +56,16 @@ Usage [...] -+---+ - - This configuration will take into account the model described in the file <<>> in version 1.0.0. It will execute the following goals in the <<>> phase: - - * {{{./java-mojo.html}java}} which will generate Java beans from the model, - - * {{{./xpp3-reader-mojo.html}xpp3-reader}} which will create an XPP reader for the model. - - [] +``` - The generated Java sources will be located in the <<>> folder (or in the folder set by the <<>> parameter), which will be added as a source folder to the project build cycle. +This configuration will take into account the model described in the file `src/main/mdo/myModel.mdo` in version 1.0.0. It will execute the following goals in the `generate-source` phase: - During the <<>> phase, it will execute the following goals: +- [java](./java-mojo.html) which will generate Java beans from the model, +- [xpp3-reader](./xpp3-reader-mojo.html) which will create an XPP reader for the model. - * {{{./xdoc-mojo.html}xdoc}} which will generate a documentation of the model in the <<>> folder, which will in turn be processed to output in the standard site, during the <<>> phase, +The generated Java sources will be located in the `target/generated-sources/modello` folder (or in the folder set by the `outputDirectory` parameter), which will be added as a source folder to the project build cycle. - * {{{./xsd-mojo.html}xsd}} which will generate an XML Schema for our model in the <<>> folder (set by the <<>> parameter), which will in turn be copied in the standard site, during the <<>> phase. +During the `pre-site` phase, it will execute the following goals: - [] +- [xdoc](./xdoc-mojo.html) which will generate a documentation of the model in the `target/generated-site/xdoc` folder, which will in turn be processed to output in the standard site, during the `site` phase, +- [xsd](./xsd-mojo.html) which will generate an XML Schema for our model in the `target/generated-site/resources/xsd` folder (set by the `outputDirectory` parameter), which will in turn be copied in the standard site, during the `site` phase. diff --git a/src/site/markdown/location-tracking.md b/src/site/markdown/location-tracking.md index 65aafa4a0..b118590d3 100644 --- a/src/site/markdown/location-tracking.md +++ b/src/site/markdown/location-tracking.md @@ -1,27 +1,14 @@ - ------ - Location Tracking - ------ - Benjamin Bentmann - ------ - 2010-04-18 - ------ +# Location Tracking -Location Tracking +Starting with Modello 1.4, some parsers (only [XPP3](./modello-plugins/modello-plugin-xpp3/index.html) in 1.4, [Snake Yaml](./modello-plugins/modello-plugin-snakeyaml/) and [Jackson](./modello-plugins/modello-plugin-jackson/) in addition in 1.8) support the tracking of line/column information for the input data. This means that additional metadata is stored in the model that can be used to query the location of some model element in the input source, e.g. for means of better error reporting to the user. - Starting with Modello 1.4, some parsers (only {{{./modello-plugins/modello-plugin-xpp3/index.html}XPP3}} in 1.4, - {{{./modello-plugins/modello-plugin-snakeyaml/}Snake Yaml}} and {{{./modello-plugins/modello-plugin-jackson/}Jackson}} in addition in 1.8) - support the tracking of line/column information for the - input data. This means that additional metadata is stored in the model that can be used to query the location of some - model element in the input source, e.g. for means of better error reporting to the user. +## Base Principle -* Base Principle +For performance reasons, generation of location metadata during parsing has to be explicitly requested. Usually, this means to use an _extended_ reader instead of the normal reader generated by Modello, for example `xpp3-extended-reader`. - For performance reasons, generation of location metadata during parsing has to be explicitly requested. Usually, this - means to use an reader instead of the normal reader generated by Modello, for example <<>>. +To store the line/column information, one class of the model has to be specifically attributed: - To store the line/column information, one class of the model has to be specifically attributed: - -+----+ +```xml Location 1.0.0+ @@ -29,27 +16,23 @@ Location Tracking -+----+ +``` - The attribute <<>> in the snippet above signals to Modello that this class should be used to record - line/column metadata during parsing. The class can be modelled as usual, but the <<>> and <<>> fields to save the line and column - number along with their accessors are automatically generated by Modello (and optional reference to source). +The attribute `locationTracker` in the snippet above signals to Modello that this class should be used to record line/column metadata during parsing. The class can be modelled as usual, but the `line` and `column` fields to save the line and column number along with their accessors are automatically generated by Modello (and optional reference to source). - A <<>> interface will be generated to factor out accessors to <<>>: +A `Tracker` interface will be generated to factor out accessors to `locationTracker`: -+----+ +```java public interface LocationTracker // named by adding "Tracker" to location tracker class name { public Location getLocation( Object field ); public void setLocation( Object field, Location location ); } -+----+ +``` - All other model classes will be equipped with a field to hold instances of the <<>> class and implement <<>> accessors to - query them. The value of <<>> attribute is used to name this field. - This way, each model class keeps track of the input locations for its fields: +All other model classes will be equipped with a field to hold instances of the `Location` class and implement `Tracker` accessors to query them. The value of `locationTracker` attribute is used to name this field. This way, each model class keeps track of the input locations for its fields: -+----+ +```java public class Model implements LocationTracker { @@ -63,19 +46,17 @@ public class Model implements LocationTracker [...] } -+----+ +``` + +## Location Map Keys -* Location Map Keys +The location map shown above is keyed by field name. An empty string is used to query the location of the bean itself (or its text contents). - The location map shown above is keyed by field name. An empty string is used to query the location of the bean itself (or its text contents). +For collections or maps, the returned `Location` instance can be further queried for its items (`Location` implements `LocationTracker`). The key to query an item depends on the type of collection. For lists the zero-based index is used, for sets the item itself is used and for maps/properties the mapping key is used. - For collections or maps, the returned <<>> instance can be further queried for its items (<<>> implements <<>>). - The key to query an item depends on the type of collection. For lists the zero-based index is used, - for sets the item itself is used and for maps/properties the mapping key is used. - - For example, consider this input XML: +For example, consider this input XML: -+----+ +```xml hello @@ -88,11 +69,11 @@ public class Model implements LocationTracker value -+----+ +``` - For this data model, one could query the location metadata like this (neglecting null checking): +For this data model, one could query the location metadata like this (neglecting null checking): -+----+ +```unknown Model model = ; // to query the location of the element itself @@ -109,14 +90,13 @@ Location location4 = model.getLocation( "setItems" ).getLocation( "set" ); // to query the location of the properties data, i.e. "value" Location location5 = model.getLocation( "properties" ).getLocation( "key" ); -+----+ +``` -* Source Tracking +## Source Tracking - Occasionally, just tracking the line/column number is not enough but the input file of the model needs to be recorded - as well. For this reason, another class of the model can be marked as a <>: +Occasionally, just tracking the line/column number is not enough but the input file of the model needs to be recorded as well. For this reason, another class of the model can be marked as a **source tracker**: -+----+ +```xml Source 1.0.0+ @@ -124,11 +104,8 @@ Location location5 = model.getLocation( "properties" ).getLocation( "key" ); -+----+ - - The fields of this source tracking class are entirely up to the application, Modello will merely extend the generated - <<>> class to support a reference to the <<>> class named after the value of <<>> attribute. +``` - An instance of the source tracking class has to be provided to the extended readers, - which will then use it to populate all the generated <<>> instances. +The fields of this source tracking class are entirely up to the application, Modello will merely extend the generated `Location` class to support a reference to the `Source` class named after the value of `sourceTracker` attribute. +An instance of the source tracking class has to be provided to the extended readers, which will then use it to populate all the generated `Location` instances. diff --git a/src/site/markdown/release-notes.md b/src/site/markdown/release-notes.md index 10d37a7a4..009dc93b9 100644 --- a/src/site/markdown/release-notes.md +++ b/src/site/markdown/release-notes.md @@ -1,612 +1,461 @@ - ------ - Release Notes - ------ - Hervé Boutemy - ------ - 2012-11-18 - ------ +# Modello -Modello +## 1.8.2 +Added ability for clients to subclass Xpp3Reader to override instantiation. This makes it possible for clients to subclass generated classes to add own features. -* 1.8.2 +MODELLO-285 - Added ability for clients to subclass Xpp3Reader to override instantiation. This makes it possible for - clients to subclass generated classes to add own features. +MODELLO-284 - MODELLO-285 +MODELLO-283 - MODELLO-284 +MODELLO-281 - MODELLO-283 +## 1.8.1 Release Notes (2013-08-12) - MODELLO-281 +Restored maven 2.2.1 compatibility that was broken in 1.8 - +## 1.8 Release Notes (2013-08-06) +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=19102) can be found in our [issue management system](./issue-management.html), and is reproduced below. -* 1.8.1 Release Notes (2013-08-12) +### Bug - Restored maven 2.2.1 compatibility that was broken in 1.8 +- \[MODELLO-209\] - Wrong handling of Map field in (XPP3|StAX|JSON|YAML)Reader/Writer with multiply association +- \[MODELLO-268\] - Dead link to Features demo +- \[MODELLO-269\] - Site => Source Repository => Web Access links in modules broken +- \[MODELLO-272\] - Wrong adder/remover generated code for association with no getter +- \[MODELLO-273\] - Generated (Xpp3|Stax|Jackson|SnakeYaml)Reader always assume modelAssociation has (g|s)etters methods +- \[MODELLO-274\] - (Jackson|SnakeYaml)ReaderGenerator can ignore the XML \`wrapped\` association style +- \[MODELLO-275\] - JSON serialization doesn't stream numbers correctly +- \[MODELLO-276\] - Nested generated Builder/Static creator methods have to take in consideration built type superclass fields +- \[MODELLO-278\] - JavaModelloGenerator is not able to generate Map code with Generic types -* 1.8 Release Notes (2013-08-06) +### New Feature - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=19102}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +- \[MODELLO-271\] - toString method is generated only of for identifier fields +- \[MODELLO-277\] - Add JSON Schema generator +- \[MODELLO-279\] - Create a SAX Writer plugin -** Bug +## 1.7 Release Notes (2013-02-19) - * [MODELLO-209] - Wrong handling of Map field in (XPP3|StAX|JSON|YAML)Reader/Writer with multiply association +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=18979) can be found in our [issue management system](./issue-management.html), and is reproduced below. - * [MODELLO-268] - Dead link to Features demo +### Bug - * [MODELLO-269] - Site => Source Repository => Web Access links in modules broken +- \[MODELLO-266\] - IllegalStateException with generated stax reader on IBM jvm +- \[MODELLO-267\] - Generated XPP3 reader fails to compile if there are any Boolean fields in the model - * [MODELLO-272] - Wrong adder/remover generated code for association with no getter +### Improvement - * [MODELLO-273] - Generated (Xpp3|Stax|Jackson|SnakeYaml)Reader always assume modelAssociation has (g|s)etters methods +- \[MODELLO-265\] - remove data/time in generated content - * [MODELLO-274] - (Jackson|SnakeYaml)ReaderGenerator can ignore the XML `wrapped` association style +## 1.6 Release Notes (2012-11) - * [MODELLO-275] - JSON serialization doesn't stream numbers correctly +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=18746) can be found in our [issue management system](./issue-management.html), and is reproduced below. - * [MODELLO-276] - Nested generated Builder/Static creator methods have to take in consideration built type superclass fields +### Bug - * [MODELLO-278] - JavaModelloGenerator is not able to generate Map code with Generic types +- \[MODELLO-251\] - Stax generated code error with class name 'File' +- \[MODELLO-256\] - Maven pom.xml plugin configuration elements are trimmed +- \[MODELLO-258\] - The xdoc for a field of type Properties contains invalid xml +- \[MODELLO-261\] - remove useJava5 and encoding parameters from non-java code generators -** New Feature +### Improvement - * [MODELLO-271] - toString method is generated only of for identifier fields +- \[MODELLO-252\] - Stax generates code which calls deperecated JRE method +- \[MODELLO-259\] - use maven-plugin-tools' java 5 annotations +- \[MODELLO-263\] - support xml:space="preserve" for DOM fields - * [MODELLO-277] - Add JSON Schema generator +### New Feature - * [MODELLO-279] - Create a SAX Writer plugin +- \[MODELLO-260\] - Support DOM type representation other than plexus-utils' Xpp3Dom objects -* 1.7 Release Notes (2013-02-19) +## 1.5 Release Notes (2011-05-30) - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=18979}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16405) can be found in our [issue management system](./issue-management.html), and is reproduced below. -** Bug +### Bug - * [MODELLO-266] - IllegalStateException with generated stax reader on IBM jvm +- \[MODELLO-249\] - Regression: char type is initialized with a '0' character instead a 0 value - * [MODELLO-267] - Generated XPP3 reader fails to compile if there are any Boolean fields in the model +### New Feature -** Improvement +- \[MODELLO-253\] - Allow the xpp3 reader to read xml fragments +- \[MODELLO-255\] - Provide error information feedback through plexus-build-api's BuildContext - * [MODELLO-265] - remove data/time in generated content +## 1.4.1 Release Notes (2010-09-25) -* 1.6 Release Notes (2012-11) +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16774) can be found in our [issue management system](./issue-management.html), and is reproduced below. - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=18746}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +### Bug -** Bug +- \[MODELLO-248\] - bad deep clone implementation when using java5 and interface associations - * [MODELLO-251] - Stax generated code error with class name 'File' +## 1.4 Release Notes (2010-05-29) - * [MODELLO-256] - Maven pom.xml plugin configuration elements are trimmed +The [full list of changes](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16153) can be found in our [issue management system](./issue-management.html), and is reproduced below. - * [MODELLO-258] - The xdoc for a field of type Properties contains invalid xml +### Bug - * [MODELLO-261] - remove useJava5 and encoding parameters from non-java code generators +- \[MODELLO-23\] - ModelloGeneratorTest is not repository independent +- \[MODELLO-52\] - Modello-core testCase broken +- \[MODELLO-226\] - Recursive descent fails for tree-like data model starting with root element +- \[MODELLO-237\] - Non-strict parsing mode doesn't properly skip over unknown elements with child elements +- \[MODELLO-245\] - Associations to same class are erroneously interpreted as bidirectional -** Improvement +### Improvement - * [MODELLO-252] - Stax generates code which calls deperecated JRE method +- \[MODELLO-206\] - improve generated XML schema for content +- \[MODELLO-239\] - Modello plugin is not thread-safe +- \[MODELLO-241\] - Remove dependency on stax-utils for StAX-based writers +- \[MODELLO-242\] - Remove dependency on plexus-utils for models that don't use DOM fields +- \[MODELLO-243\] - Add read() methods that take InputStream as data source +- \[MODELLO-244\] - Add write() methods that marshal to output stream +- \[MODELLO-246\] - Make non-strict parsing ignore text inside element-only sections - * [MODELLO-259] - use maven-plugin-tools' java 5 annotations +### New Feature - * [MODELLO-263] - support xml:space="preserve" for DOM fields +- \[MODELLO-85\] - Allow an element to have a text and attributes at the same time +- \[MODELLO-240\] - Provide support to track line/column number of source elements -** New Feature +## 1.3 Release Notes (2010-04-01) - * [MODELLO-260] - Support DOM type representation other than plexus-utils' Xpp3Dom objects +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15584), and is reproduced below. -* 1.5 Release Notes (2011-05-30) +### Bug - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16405}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +- \[MODELLO-234\] - XML readers' generated code doesn't compile if root xml.tagName contains a dot or minus +- \[MODELLO-235\] - Can't null association fields when java.useInterface=true -** Bug +### Improvement - * [MODELLO-249] - Regression: char type is initialized with a '0' character instead a 0 value +- \[MODELLO-236\] - add XML Schema reference to generated xdoc -** New Feature +### New Feature - * [MODELLO-253] - Allow the xpp3 reader to read xml fragments +- \[MODELLO-214\] - Add Java annotations generation - * [MODELLO-255] - Provide error information feedback through plexus-build-api's BuildContext +### Task -* 1.4.1 Release Notes (2010-09-25) +- \[MODELLO-230\] - upgrade Modello code to Java 5 (without changing generated code: Java 1.4 code still generated by default) - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16774}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +### Wish -** Bug +- \[MODELLO-231\] - remove name and description elements from codeSegment in Modello's meta-model - * [MODELLO-248] - bad deep clone implementation when using java5 and interface associations +## 1.2 Release Notes (2010-01-19) -* 1.4 Release Notes (2010-05-29) +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15583), and is reproduced below. - The {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=16153}full list of changes}} can be found in our {{{./issue-management.html}issue management system}}, and is reproduced below. +### Bug -** Bug +- \[MODELLO-168\] - Recursive descent fails for tree-like data model +- \[MODELLO-176\] - Strict mode does not detect problems when data fields are encoded as XML attributes +- \[MODELLO-222\] - java5 associations do not respect java.useInterface - * [MODELLO-23] - ModelloGeneratorTest is not repository independent +### Improvement - * [MODELLO-52] - Modello-core testCase broken +- \[MODELLO-224\] - XML representation of inherited fields: allow more flexibility than only append at end +- \[MODELLO-229\] - Improve Modello model documentation: fields order is counter intuitive - * [MODELLO-226] - Recursive descent fails for tree-like data model starting with root element +## 1.1 Release Notes (2009-08-21) - * [MODELLO-237] - Non-strict parsing mode doesn't properly skip over unknown elements with child elements +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14908), and is reproduced below. - * [MODELLO-245] - Associations to same class are erroneously interpreted as bidirectional +### Bug -** Improvement +- \[MODELLO-200\] - Not possible to read older version of xml file if there is an unrecognized tag even if "strict" is set to false +- \[MODELLO-201\] - XSD generator fails on field type Set\ +- \[MODELLO-207\] - Transient feature does not allow generate self Model +- \[MODELLO-208\] - class cast assertion to wrong type in one multiplicity association setter when using java.useInterface - * [MODELLO-206] - improve generated XML schema for content +### Improvement - * [MODELLO-239] - Modello plugin is not thread-safe +- \[MODELLO-181\] - Add @SuppressWarnings to all generated sources if Java 5 is enabled +- \[MODELLO-185\] - add Content type support to stax plugin +- \[MODELLO-203\] - add Content type support to dom4j plugin +- \[MODELLO-210\] - Misspelling by AbstractModelloGenerator#singular(..) method - * [MODELLO-241] - Remove dependency on stax-utils for StAX-based writers +### New Feature - * [MODELLO-242] - Remove dependency on plexus-utils for models that don't use DOM fields +- \[MODELLO-191\] - Add support to generate clone() methods +- \[MODELLO-205\] - Allow to exclude fields from parser/writer - * [MODELLO-243] - Add read() methods that take InputStream as data source +### Wish - * [MODELLO-244] - Add write() methods that marshal to output stream +- \[MODELLO-165\] - remove classCastAssertion - * [MODELLO-246] - Make non-strict parsing ignore text inside element-only sections +## 1.0.2 Release Notes (2009-06-11) -** New Feature +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15080), and is reproduced below. - * [MODELLO-85] - Allow an element to have a text and attributes at the same time +### Bug - * [MODELLO-240] - Provide support to track line/column number of source elements +- \[MODELLO-88\] - converters goal generates wrong class names for continuum-model - won't compile +- \[MODELLO-188\] - Modello plugins are not available from ModelloCli or a standalone Modello instance +- \[MODELLO-189\] - Generated Xpp3Reader does not reconstruct modelEncoding +- \[MODELLO-199\] - java.getter attribute for field not initialize at all +### Improvement -* 1.3 Release Notes (2010-04-01) +- \[MODELLO-190\] - Use StringBuilder for toString() when Java 1.5 is enabled - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15584}issue management system}}, and is reproduced below. +## 1.0.1 Release Notes (2009-03-09) -** Bug +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14892), and is reproduced below. - * [MODELLO-234] - XML readers' generated code doesn't compile if root xml.tagName contains a dot or minus +### Bug - * [MODELLO-235] - Can't null association fields when java.useInterface=true +- \[MODELLO-167\] - bi-directional association makes an OutOfMemoryException with xdoc plugin +- \[MODELLO-174\] - Wrong XDoc for flat lists +- \[MODELLO-184\] - Generated XSD is invalid for a field with "Content" type +- \[MODELLO-187\] - add Content type support to xdoc plugin -** Improvement +### Improvement - * [MODELLO-236] - add XML Schema reference to generated xdoc +- \[MODELLO-172\] - Add timestamp and the generator in the generated files +- \[MODELLO-173\] - Ignore leading/trailing whitespace of field descriptions when generating accessor comments +- \[MODELLO-177\] - running modello generation during IDE incremental build +- \[MODELLO-178\] - add xml.format="long" option to read/write a date field as a long value -** New Feature +### New Feature - * [MODELLO-214] - Add Java annotations generation +- \[MODELLO-179\] - add a type column in xdoc to describe fields types -** Task +### Task - * [MODELLO-230] - upgrade Modello code to Java 5 (without changing generated code: Java 1.4 code still generated by default) +- \[MODELLO-182\] - Make tests respect maven.repo.local +### Wish -** Wish +- \[MODELLO-180\] - Avoid unused imports - * [MODELLO-231] - remove name and description elements from codeSegment in Modello's meta-model +## 1.0 Release Notes (2009-01-29) +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13956), and is reproduced below. -* 1.2 Release Notes (2010-01-19) +### Bug - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15583}issue management system}}, and is reproduced below. +- \[MODELLO-126\] - Date formats supported by XML readers/writers are not consistent across plugins +- \[MODELLO-141\] - XsdGenerator should throw an exception when no namespace was defined instead of using the POM namespace +- \[MODELLO-142\] - EOL is not handled correctly in the XMLWriter +- \[MODELLO-146\] - String\[\] not supported in java plugin +- \[MODELLO-147\] - fix for building with newer maven +- \[MODELLO-149\] - Support xml.namespace and xml.schemaLocation attributes in dom4j plugin +- \[MODELLO-150\] - float field without default value in model generates invalid java code +- \[MODELLO-151\] - geneated java source imports avery classes, even those which are disabled +- \[MODELLO-152\] - Strict parsing mode doesn't detect missing root element +- \[MODELLO-153\] - Default value doesn't work for attributes. +- \[MODELLO-154\] - xsd plugin does not honour xml.associationTagName +- \[MODELLO-158\] - trying to generate an interface with a codeSegment causes an infinite loop +- \[MODELLO-160\] - some internal links are wrong -** Bug +### Improvement - * [MODELLO-168] - Recursive descent fails for tree-like data model +- \[MODELLO-101\] - Support xml.namespace and xml.schemaLocation attributes in xpp3 plugin +- \[MODELLO-102\] - Generate model classes with JDK 1.5 Generics +- \[MODELLO-104\] - Remove support for "model" parameter and make the "models" parameter @required +- \[MODELLO-139\] - add encoding support to CLI +- \[MODELLO-155\] - support $version in xml.namespace, xsd.namespace and xsd.target-namespace (like xml.schemaLocation) +- \[MODELLO-156\] - avoid namespace information duplication in model: xml.namespace, xsd.namespace and xsd.target-namespace +- \[MODELLO-159\] - improve xdoc representation of properties - * [MODELLO-176] - Strict mode does not detect problems when data fields are encoded as XML attributes +### New Feature - * [MODELLO-222] - java5 associations do not respect java.useInterface +- \[MODELLO-143\] - add an option to xdoc to add a separator before a field documentation +- \[MODELLO-145\] - Create an XSD for Modello -** Improvement +### Task - * [MODELLO-224] - XML representation of inherited fields: allow more flexibility than only append at end +- \[MODELLO-21\] - Move the Java plugin out of core. +- \[MODELLO-135\] - modelEncoding attribute should be available in root class only +- \[MODELLO-138\] - improve API consistency between readers generated by different plugins - * [MODELLO-229] - Improve Modello model documentation: fields order is counter intuitive +### Wish +- \[MODELLO-136\] - parseXXX methods in generated writers should be private instead of public +- \[MODELLO-157\] - move xml.namespace and xml.schemaLocation attributes from class element (where rootElemen="true") to model +- \[MODELLO-162\] - move xml.listStyle from field attribute to association attribute, like xml.mapStyle +- \[MODELLO-163\] - transform Modello xml.associationTagName in field element to xml.tagName in association element +- \[MODELLO-164\] - move java.adder from field attribute to association attribute +- \[MODELLO-166\] - remove java.generate-remove association attribute +- \[MODELLO-169\] - rename xsd.target-namespace attribute to xsd.targetNamespace to be more consistent with other attributes +- \[MODELLO-170\] - replace java.generate-create and java.generate-break attributes with java.bidi +- \[MODELLO-171\] - rename java.use-interface attribute to java.useInterface to be more consistent with other attributes -* 1.1 Release Notes (2009-08-21) +## 1.0-alpha-22 Release Notes (2008-12-12) - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14908}issue management system}}, and is reproduced below. +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14742), and is reproduced below. -** Bug +### Bug - * [MODELLO-200] - Not possible to read older version of xml file if there is an unrecognized tag even if "strict" is set to false +- \[MODELLO-119\] - \[REGRESSION\] strict flag doesn't fail on elements that aren't part of the model +- \[MODELLO-125\] - generated java source for method signatures don't follow coding style +- \[MODELLO-127\] - Dom4j plugin should support xml.format attribute +- \[MODELLO-128\] - add support for byte and short to xsd plugin +- \[MODELLO-129\] - xsd plugin does generate an invalid schema for Properties type +- \[MODELLO-130\] - Date support in xsd plugin is broken +- \[MODELLO-132\] - char default value not supported by java plugin +- \[MODELLO-134\] - fix byte type support +- \[MODELLO-137\] - default values not supported for float and long types - * [MODELLO-201] - XSD generator fails on field type Set +### Improvement - * [MODELLO-207] - Transient feature does not allow generate self Model +- \[MODELLO-121\] - Add xsd support for Boolean attributes +- \[MODELLO-124\] - create a shared test model to check common features support in every plugin +- \[MODELLO-133\] - add char support in xsd plugin - * [MODELLO-208] - class cast assertion to wrong type in one multiplicity association setter when using java.useInterface +### Task -** Improvement +- \[MODELLO-131\] - remove modello modules relying on components being phased-out - * [MODELLO-181] - Add @SuppressWarnings to all generated sources if Java 5 is enabled +## 1.0-alpha-21 Release Notes (2008-08-06) - * [MODELLO-185] - add Content type support to stax plugin +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14469), and is reproduced below. - * [MODELLO-203] - add Content type support to dom4j plugin +### Bug - * [MODELLO-210] - Misspelling by AbstractModelloGenerator#singular(..) method +- \[MODELLO-114\] - Generated xsd is wrong when multiplicity is 1 +- \[MODELLO-115\] - Not possible to configure the file name for generated xdoc with the xdoc mojo +- \[MODELLO-117\] - Not possible to configure the file name for generated xsd with the xsd mojo -** New Feature +### Improvement - * [MODELLO-191] - Add support to generate clone() methods +- \[MODELLO-116\] - generated xdoc doesn't display attribute when the field is an attribute - * [MODELLO-205] - Allow to exclude fields from parser/writer +### New Feature -** Wish +- \[MODELLO-113\] - Parsing xml element with attributes and a getter to the element content - * [MODELLO-165] - remove classCastAssertion +## 1.0-alpha-20 Release Notes (2008-07-25) +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14466), and is reproduced below. -* 1.0.2 Release Notes (2009-06-11) +### Bug - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=15080}issue management system}}, and is reproduced below. +- \[MODELLO-112\] - strict flag not considered for handling of invalid nested elements within an association list. -** Bug +## 1.0-alpha-19 Release Notes (2008-07-14) - * [MODELLO-88] - converters goal generates wrong class names for continuum-model - won't compile +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14339), and is reproduced below. - * [MODELLO-188] - Modello plugins are not available from ModelloCli or a standalone Modello instance +### Bug - * [MODELLO-189] - Generated Xpp3Reader does not reconstruct modelEncoding +- \[MODELLO-105\] - Handle double and float types +- \[MODELLO-107\] - modello-maven-plugin don't close opened files +- \[MODELLO-111\] - Binary compatibility broken in generated XPP3 Reader classes - * [MODELLO-199] - java.getter attribute for field not initialize at all +### Improvement -** Improvement +- \[MODELLO-94\] - Added java.net repository - * [MODELLO-190] - Use StringBuilder for toString() when Java 1.5 is enabled +### New Feature +- \[MODELLO-109\] - add an "encoding" parameter and use ${project.build.sourceEncoding} as default value -* 1.0.1 Release Notes (2009-03-09) +### Task - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14892}issue management system}}, and is reproduced below. +- \[MODELLO-110\] - remove copy of plexus-utils' XML encoding support sources -** Bug +## 1.0-alpha-18 Release Notes (2008-01-15) - * [MODELLO-167] - bi-directional association makes an OutOfMemoryException with xdoc plugin +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13717), and is reproduced below. - * [MODELLO-174] - Wrong XDoc for flat lists +### Bug - * [MODELLO-184] - Generated XSD is invalid for a field with "Content" type +- \[MODELLO-68\] - Strict parsing lists +- \[MODELLO-72\] - Generated code should be clean of warnings +- \[MODELLO-83\] - Improvements for the generated methods equals(...), hashCode(), toString() +- \[MODELLO-86\] - modello-plugin-converters fails test +- \[MODELLO-87\] - xml.tagName not used to generate xdoc and xsd +- \[MODELLO-95\] - AbstractModelloGenerator#singular( String name ) could throw NPE and return empty string +- \[MODELLO-98\] - Reader doesn't handle _defaultValue/_ +- \[MODELLO-99\] - When a class is marked as abstract the xpp3 reader still wants to generate constructors for it... +- \[MODELLO-108\] - Generated JDOMWriter throws ConcurrentModificationException when updating Xpp3Dom objects - * [MODELLO-187] - add Content type support to xdoc plugin +### Improvement -** Improvement +- \[MODELLO-45\] - Generated java sources should not have javadoc where _description_ was not specified. +- \[MODELLO-49\] - Support for xml.attribute and xml.listStyle="flat" is missing in xsd plugin +- \[MODELLO-56\] - Major modello-plugin-xdoc rewrite +- \[MODELLO-66\] - Create possibility to have the same set of executions for several models in modello-maven-plugin +- \[MODELLO-100\] - Add hyperlinks to associations in element descriptor table like it is done in model descriptor - * [MODELLO-172] - Add timestamp and the generator in the generated files +## 1.0-alpha-17 Release Notes (2007-07-30) - * [MODELLO-173] - Ignore leading/trailing whitespace of field descriptions when generating accessor comments +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13637), and is reproduced below. - * [MODELLO-177] - running modello generation during IDE incremental build +### Bug - * [MODELLO-178] - add xml.format="long" option to read/write a date field as a long value +- \[MODELLO-92\] - XML encoding support for *.mdo files +- \[MODELLO-96\] - Add more javadoc comments in the generated classes -** New Feature +## 1.0-alpha-15 Release Notes (2007-03-23) - * [MODELLO-179] - add a type column in xdoc to describe fields types +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13272), and is reproduced below. -** Task +### Bug - * [MODELLO-182] - Make tests respect maven.repo.local +- \[MODELLO-46\] - make namespace of generated xsd configurable +- \[MODELLO-84\] - Clean list in the registry before to rewrite it +### Improvement -** Wish +- \[MODELLO-67\] - Add option for JPOX mapping file to be in model package \[Patch included\] - * [MODELLO-180] - Avoid unused imports +## 1.0-alpha-14 Release Notes (2007-02-20) +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13068), and is reproduced below. -* 1.0 Release Notes (2009-01-29) +### Bug - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13956}issue management system}}, and is reproduced below. +- \[MODELLO-69\] - Validation of the top level element +- \[MODELLO-74\] - Test errors in modello-plugin-stax on Windows XP + Cygwin +- \[MODELLO-75\] - NPE in plexus init +- \[MODELLO-76\] - Can't build modello-maven-plugin +- \[MODELLO-79\] - Modello maven plugin doesn't compile with maven 2.0.x +- \[MODELLO-80\] - Plexus doesn't call initialise() method in DefaultVelocityComponent with maven-2.0.x +- \[MODELLO-82\] - No carriage return for the last curly bracket -** Bug +### New Feature - * [MODELLO-126] - Date formats supported by XML readers/writers are not consistent across plugins +- \[MODELLO-77\] - Add a read method with a path to allow to resolve relative entities +- \[MODELLO-78\] - Show an optional column containing the model version in which an element was added - * [MODELLO-141] - XsdGenerator should throw an exception when no namespace was defined instead of using the POM namespace +### Task - * [MODELLO-142] - EOL is not handled correctly in the XMLWriter +- \[MODELLO-58\] - update modello's parent POM - * [MODELLO-146] - String[] not supported in java plugin +## 1.0-alpha-13 Release Notes (2006-12-07) - * [MODELLO-147] - fix for building with newer maven +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=12956), and is reproduced below. - * [MODELLO-149] - Support xml.namespace and xml.schemaLocation attributes in dom4j plugin +### Bug - * [MODELLO-150] - float field without default value in model generates invalid java code +- \[MODELLO-53\] - java.lang.StackOverflowError when generating an xdoc for a modello model +- \[MODELLO-54\] - Generate tag name instead of association tag name +- \[MODELLO-73\] - Xml output doesn't use OS line separator, so tests in continuum or plexus-security failed on windows - * [MODELLO-151] - geneated java source imports avery classes, even those which are disabled +### Improvement - * [MODELLO-152] - Strict parsing mode doesn't detect missing root element +- \[MODELLO-47\] - Create goal pages on the site that describes how to use the modello-maven-plugin +- \[MODELLO-50\] - \[patch\] Add support for the class/field/defaultValue element +- \[MODELLO-65\] - Add in the DOM4J reader an URL parameter (to allow to use relative entities in XML) - * [MODELLO-153] - Default value doesn't work for attributes. +## 1.0-alpha-11 Release Notes (2006-09-20) - * [MODELLO-154] - xsd plugin does not honour xml.associationTagName +The full list of changes can be found in our [issue management system](http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=12790), and is reproduced below. - * [MODELLO-158] - trying to generate an interface with a codeSegment causes an infinite loop +### Bug - * [MODELLO-160] - some internal links are wrong +- \[MODELLO-51\] - Xpp3GeneratorTest failed for date format on french system +- \[MODELLO-57\] - Dom4jGeneratorTest failed for date format on french system +- \[MODELLO-61\] - \[jdom-plugin\] data loss when writing repository/pluginRepository in maven's settings.xml -** Improvement +### Improvement - * [MODELLO-101] - Support xml.namespace and xml.schemaLocation attributes in xpp3 plugin +- \[MODELLO-48\] - Support for xml.attribute and xml.listStyle in generated xdoc +- \[MODELLO-64\] - Allow generating jpox package.jdo in different places than META-INF. - * [MODELLO-102] - Generate model classes with JDK 1.5 Generics - - * [MODELLO-104] - Remove support for "model" parameter and make the "models" parameter @required - - * [MODELLO-139] - add encoding support to CLI - - * [MODELLO-155] - support ${version} in xml.namespace, xsd.namespace and xsd.target-namespace (like xml.schemaLocation) - - * [MODELLO-156] - avoid namespace information duplication in model: xml.namespace, xsd.namespace and xsd.target-namespace - - * [MODELLO-159] - improve xdoc representation of properties - -** New Feature - - * [MODELLO-143] - add an option to xdoc to add a separator before a field documentation - - * [MODELLO-145] - Create an XSD for Modello - -** Task - - * [MODELLO-21] - Move the Java plugin out of core. - - * [MODELLO-135] - modelEncoding attribute should be available in root class only - - * [MODELLO-138] - improve API consistency between readers generated by different plugins - - -** Wish - - * [MODELLO-136] - parseXXX methods in generated writers should be private instead of public - - * [MODELLO-157] - move xml.namespace and xml.schemaLocation attributes from class element (where rootElemen="true") to model - - * [MODELLO-162] - move xml.listStyle from field attribute to association attribute, like xml.mapStyle - - * [MODELLO-163] - transform Modello xml.associationTagName in field element to xml.tagName in association element - - * [MODELLO-164] - move java.adder from field attribute to association attribute - - * [MODELLO-166] - remove java.generate-remove association attribute - - * [MODELLO-169] - rename xsd.target-namespace attribute to xsd.targetNamespace to be more consistent with other attributes - - * [MODELLO-170] - replace java.generate-create and java.generate-break attributes with java.bidi - - * [MODELLO-171] - rename java.use-interface attribute to java.useInterface to be more consistent with other attributes - - -* 1.0-alpha-22 Release Notes (2008-12-12) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14742}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-119] - [REGRESSION] strict flag doesn't fail on elements that aren't part of the model - - * [MODELLO-125] - generated java source for method signatures don't follow coding style - - * [MODELLO-127] - Dom4j plugin should support xml.format attribute - - * [MODELLO-128] - add support for byte and short to xsd plugin - - * [MODELLO-129] - xsd plugin does generate an invalid schema for Properties type - - * [MODELLO-130] - Date support in xsd plugin is broken - - * [MODELLO-132] - char default value not supported by java plugin - - * [MODELLO-134] - fix byte type support - - * [MODELLO-137] - default values not supported for float and long types - -** Improvement - - * [MODELLO-121] - Add xsd support for Boolean attributes - - * [MODELLO-124] - create a shared test model to check common features support in every plugin - - * [MODELLO-133] - add char support in xsd plugin - -** Task - - * [MODELLO-131] - remove modello modules relying on components being phased-out - - -* 1.0-alpha-21 Release Notes (2008-08-06) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14469}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-114] - Generated xsd is wrong when multiplicity is 1 - - * [MODELLO-115] - Not possible to configure the file name for generated xdoc with the xdoc mojo - - * [MODELLO-117] - Not possible to configure the file name for generated xsd with the xsd mojo - -** Improvement - - * [MODELLO-116] - generated xdoc doesn't display attribute when the field is an attribute - -** New Feature - - * [MODELLO-113] - Parsing xml element with attributes and a getter to the element content - - -* 1.0-alpha-20 Release Notes (2008-07-25) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14466}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-112] - strict flag not considered for handling of invalid nested elements within an association list. - - -* 1.0-alpha-19 Release Notes (2008-07-14) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=14339}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-105] - Handle double and float types - - * [MODELLO-107] - modello-maven-plugin don't close opened files - - * [MODELLO-111] - Binary compatibility broken in generated XPP3 Reader classes - -** Improvement - - * [MODELLO-94] - Added java.net repository - -** New Feature - - * [MODELLO-109] - add an "encoding" parameter and use $\{project.build.sourceEncoding\} as default value - -** Task - - * [MODELLO-110] - remove copy of plexus-utils' XML encoding support sources - - -* 1.0-alpha-18 Release Notes (2008-01-15) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13717}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-68] - Strict parsing lists - - * [MODELLO-72] - Generated code should be clean of warnings - - * [MODELLO-83] - Improvements for the generated methods equals(...), hashCode(), toString() - - * [MODELLO-86] - modello-plugin-converters fails test - - * [MODELLO-87] - xml.tagName not used to generate xdoc and xsd - - * [MODELLO-95] - AbstractModelloGenerator#singular( String name ) could throw NPE and return empty string - - * [MODELLO-98] - Reader doesn't handle - - * [MODELLO-99] - When a class is marked as abstract the xpp3 reader still wants to generate constructors for it... - - * [MODELLO-108] - Generated JDOMWriter throws ConcurrentModificationException when updating Xpp3Dom objects - -** Improvement - - * [MODELLO-45] - Generated java sources should not have javadoc where was not specified. - - * [MODELLO-49] - Support for xml.attribute and xml.listStyle="flat" is missing in xsd plugin - - * [MODELLO-56] - Major modello-plugin-xdoc rewrite - - * [MODELLO-66] - Create possibility to have the same set of executions for several models in modello-maven-plugin - - * [MODELLO-100] - Add hyperlinks to associations in element descriptor table like it is done in model descriptor - - -* 1.0-alpha-17 Release Notes (2007-07-30) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13637}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-92] - XML encoding support for *.mdo files - - * [MODELLO-96] - Add more javadoc comments in the generated classes - - -* 1.0-alpha-15 Release Notes (2007-03-23) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13272}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-46] - make namespace of generated xsd configurable - - * [MODELLO-84] - Clean list in the registry before to rewrite it - -** Improvement - - * [MODELLO-67] - Add option for JPOX mapping file to be in model package [Patch included] - - -* 1.0-alpha-14 Release Notes (2007-02-20) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=13068}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-69] - Validation of the top level element - - * [MODELLO-74] - Test errors in modello-plugin-stax on Windows XP + Cygwin - - * [MODELLO-75] - NPE in plexus init - - * [MODELLO-76] - Can't build modello-maven-plugin - - * [MODELLO-79] - Modello maven plugin doesn't compile with maven 2.0.x - - * [MODELLO-80] - Plexus doesn't call initialise() method in DefaultVelocityComponent with maven-2.0.x - - * [MODELLO-82] - No carriage return for the last curly bracket - - -** New Feature - - * [MODELLO-77] - Add a read method with a path to allow to resolve relative entities - - * [MODELLO-78] - Show an optional column containing the model version in which an element was added - -** Task - - * [MODELLO-58] - update modello's parent POM - - -* 1.0-alpha-13 Release Notes (2006-12-07) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=12956}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-53] - java.lang.StackOverflowError when generating an xdoc for a modello model - - * [MODELLO-54] - Generate tag name instead of association tag name - - * [MODELLO-73] - Xml output doesn't use OS line separator, so tests in continuum or plexus-security failed on windows - -** Improvement - - * [MODELLO-47] - Create goal pages on the site that describes how to use the modello-maven-plugin - - * [MODELLO-50] - [patch] Add support for the class/field/defaultValue element - - * [MODELLO-65] - Add in the DOM4J reader an URL parameter (to allow to use relative entities in XML) - - -* 1.0-alpha-11 Release Notes (2006-09-20) - - The full list of changes can be found in our {{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10510&version=12790}issue management system}}, and is reproduced below. - -** Bug - - * [MODELLO-51] - Xpp3GeneratorTest failed for date format on french system - - * [MODELLO-57] - Dom4jGeneratorTest failed for date format on french system - - * [MODELLO-61] - [jdom-plugin] data loss when writing repository/pluginRepository in maven's settings.xml - -** Improvement - - * [MODELLO-48] - Support for xml.attribute and xml.listStyle in generated xdoc - - * [MODELLO-64] - Allow generating jpox package.jdo in different places than META-INF.