Maven 2.x Changes Plugin

HTML inside <action/> is swallowed

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-beta-3
  • Component/s: changes.xml
  • Labels:
    None
  • Number of attachments :
    0

Description

eg:

<action dev="vmassol" type="fix" issue="MPCHANGES-14">
Added sorting of <code><action></code> elements. It is controlled
by 2 properties. The <code>maven.changes.sort</code> property decides
whether sorting is enabled or not and the
<code>maven.changes.sort.order</code> one decides the sort order.
Defaults to <code>add,fix,update,remove</code>.
</action>

comes out as:
. Fixes MPCHANGES-14

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Johnny R. Ruiz III added a comment -

Fixed.

Text containing html tags must be enclosed in a <![CDATA[ <YOUR TEXT HERE> ]]> for this to work.

<![CDATA[ <YOUR TEXT HERE> ]]> --> is this the correct approach for this problem? any ideas?

Show
Johnny R. Ruiz III added a comment - Fixed. Text containing html tags must be enclosed in a <![CDATA[ <YOUR TEXT HERE> ]]> for this to work. <![CDATA[ <YOUR TEXT HERE> ]]> --> is this the correct approach for this problem? any ideas?
Hide
Permalink
Brett Porter added a comment -

I'd rather it be backwards compatible if possible. If it's a big problem though, I wouldn't worry about it.

Show
Brett Porter added a comment - I'd rather it be backwards compatible if possible. If it's a big problem though, I wouldn't worry about it.
Hide
Permalink
Johnny R. Ruiz III added a comment -

Fixed

Show
Johnny R. Ruiz III added a comment - Fixed
Hide
Permalink
Jörg Hohwiller added a comment -

It works with CDATA as workaround.
With 2.0-beta-3 it still does NOT work without the workaround.
This is sort of nasty to me.
It would be very nice if this was really fixed in further releases.

Show
Jörg Hohwiller added a comment - It works with CDATA as workaround. With 2.0-beta-3 it still does NOT work without the workaround. This is sort of nasty to me. It would be very nice if this was really fixed in further releases.
Hide
Permalink
Jörg Hohwiller added a comment -

BTW it does not really make sense to be backward compatible in error situations.
The result is that HTML tags are "striped out" without a trace.
So "foo <code>bar</code>" becomes "foo ".
I can not see why this behavior should be preserved?

Show
Jörg Hohwiller added a comment - BTW it does not really make sense to be backward compatible in error situations. The result is that HTML tags are "striped out" without a trace. So "foo <code>bar</code>" becomes "foo ". I can not see why this behavior should be preserved?

People

  • Assignee:
    Johnny R. Ruiz III
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: