On Fri, 22 Nov 2024 at 13:06, Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote: > > Hi Sławek, > > On 22.11.2024 08:33, Slawomir Jaranowski wrote: > > I'm working on maven-changes-plugin - this project hasn't been > > released for a long time, so it is time to refresh it and release it. > > > > I need to make changes in schema - the newer version of modello > > doesn't support mixed tags - tags with content and other tags. > > It will breaking changes, you will need to change your changes.xml a little. > > That sound great! > > Since 3.0.0 will be a major release, might you consider additional > changes to the schema?
Why not? > > Due to the endless merge conflicts that the current monolithic > `changes.xml` file generates, in Apache Log4j we switched to a custom > `log4j-changelog-maven-plugin` that splits the changelog entries into > multiple files (see [1] for the documentation). > > I am not particularly attached to maintaining yet another changelog > plugin and I would gladly switch back to `maven-changes-plugin` if it > would support the following features: > > * An alternative changelog structure that would allow entries to be > split into separate files. > > * Some small changes to the supported action types: we have an > additional `change` action to mark behavioral changes that require a > `MINOR` semantic version bump. > > * It would be nice to have a goal that checks if the version bump is > adequate for the changes. Currently we use the following rules: `remove` > requires a `MAJOR` bump, `add` and `change` a `MINOR` bump, `fix` a > `PATCH` bump. The `update` action is mostly used for irrelevant changes > (like Dependabot's dependency upgrades). > > * We currently have an attribute for descriptions that tells us the type > of markup is used in descriptions (we always use AsciiDoc, but that > could change). Not sure if this information can be used at this time, > but maybe it could be useful in the future. > > At this moment I don't have time to work on these features, but maybe > you could review the XML schema, to facilitate the introduction of these > features in 3.1.x without further breaking changes. What do you think? > Thanks for sharing ideas ... If you can create issues with a proposition of new features, we will have it on the list and maybe someone implemented it. My idea was only to refresh a little bit ;-) > Piotr > > [1] https://logging.apache.org/log4j/tools/log4j-changelog.html > -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
