It shouldn't if you don't specify any commentSeparator.
It should be completely backward compatible, but please verify.
On 28 Nov 2013, at 12:30, "Paul B." <iwebdeve...@gmail.com> wrote:
> Quick question... Just curious if this will affect any custom string
> converters? We use a few custom string converters to resolve uri's passed in
> via maven properties, so in the stories we can currently pass in some thing
> like #{test.uri} in the examples table...
>
> Haven't got the chance yet to test this out with inline comments, but thought
> it maybe worth asking...
>
> Cheers,
> P
>
>
>
> Sent from my MetroPCS 4G Wireless Phone
>
>
>
> -------- Original message --------
> From: "Mauro Talevi (JIRA)" <j...@codehaus.org>
> Date: 11/27/2013 11:50 AM (GMT-05:00)
> To: dev@jbehave.codehaus.org
> Subject: [jbehave-dev] [jira] (JBEHAVE-962) Inline Comments
>
>
>
>
> Mauro Talevi commented on JBEHAVE-962
> Inline Comments
> Thanks for testing. The trimming should be the default. It has been fixed and
> will be available in the next release.
>
> The comments in the table values are a rather specific use case, and using
> inline property allows the user to specify the comment separator of
> preference. Using | would not work as it would be mistaken for a column
> separator, while !-- seemed less readable (but you can configure it you
> prefer).
>
> Let's see how this works and we can do an enhancement later on, if needed.
>
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
> --------------------------------------------------------------------- To
> unsubscribe from this list, please visit:
> http://xircles.codehaus.org/manage_email
