Why not have separate <action> entries for each change instead of this one
big thingy:
<action dev="ggregory" type="update">
- org.eclipse.persistence:javax.persistence ............. 2.1.1 -> 2.2.1
- org.eclipse.persistence:org.eclipse.persistence.jpa ... 2.6.5 -> 2.6.9
- org.fusesource.jansi:jansi ............................ 2.3.1 -> 2.3.2
- net.javacrumbs.json-unit:json-unit .................. 2.24.0 -> 2.25.0
- org.liquibase:liquibase-core .......................... 3.5.3 -> 3.5.5
- org.springframework:spring-aop ........................ 5.3.3 -> 5.3.5
- org.springframework:spring-beans ...................... 5.3.3 -> 5.3.5
- org.springframework:spring-context .................... 5.3.3 -> 5.3.5
- org.springframework:spring-context-support ............ 5.3.3 -> 5.3.5
- org.springframework:spring-core ....................... 5.3.3 -> 5.3.5
- org.springframework:spring-expression ................. 5.3.3 -> 5.3.5
- org.springframework:spring-oxm ........................ 5.3.3 -> 5.3.5
- org.springframework:spring-test ....................... 5.3.3 -> 5.3.5
- org.springframework:spring-web ........................ 5.3.3 -> 5.3.5
- org.springframework:spring-webmvc ..................... 5.3.3 -> 5.3.5
- org.tukaani:xz ............................................ 1.8 -> 1.9
</action>
On Wed, Dec 8, 2021 at 11:09 PM Apache <ralph.go...@dslextreme.com> wrote:
> I tried that. Somehow the whole description got removed. Even if that
> worked the release notes would look terrible.
>
> Ralph.
>
> > On Dec 8, 2021, at 5:23 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> >
> > If you refer to
> > https://logging.staged.apache.org/log4j/2.x/changes-report.html#a2.15.0
> I'm
> > not sure what we can do unless there is special sauce to use in
> > changes.xml. Are we supposed to use HTML in a changes.xml entry? That
> would
> > be simple enough.
> >
> > Gary
> >
> >> On Tue, Dec 7, 2021 at 5:05 PM Ralph Goers <ralph.go...@dslextreme.com>
> >> wrote:
> >>
> >> Gary,
> >>
> >> Please review the manual changes for 2.15.0 on the staging web site. The
> >> last item is yours from
> >> upgrading a bunch of dependency versions.
> >>
> >> I spent a bunch of time yesterday trying to figure out how to make that
> >> pretty and finally gave up.
> >> It requires knowing now the changes plugin passes data to Doxia and what
> >> Doxia is going to do to
> >> render it. If you look at
> >>
> https://github.com/apache/maven-changes-plugin/blob/master/src/main/java/org/apache/maven/plugins/changes/ChangesReportGenerator.java
> >> in the constructAction methodyou will see that it calls sink.text() for
> >> the description. I can only guess
> >> it is using Doxia’s XHTML Sink which just appends the data to a
> >> StringBuffer.
> >>
> >> Interestingly, it doesn’t look to bad when the announcement goal is run,
> >> but that is only because the
> >> target is a Markdown file so it sort of looks ok, although Markdown
> seems
> >> to treat it as one large code block.
> >>
> >> Bottom line - Unless you can figure out how to get these to properly
> >> format entries like this will
> >> continue to be a mess in the future. I know we have had at least one
> like
> >> it in the past.
> >>
> >> Ralph
> >>
>
>
>
