Preserving backwards compatibility?

View: New views
2 Messages — Rating Filter:   Alert me  

Preserving backwards compatibility?

by dfabulich :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


In revisions 598168 and 598171 I added support for an "aggregate" mode to
the surefire-report plugin.  In this mode, the plugin will aggregate XML
test results from multiple directories, just like the javadoc and jxr
plugins.

In 2.3, surefire-report takes exactly one "reportDirectory".  In 2.4, the
plugin now accepts an array of "reportDirectories".

In order to maintain backwards compatibility, I continued to accept the
old "reportDirectory" property, marking it with the "@deprecated" javadoc
attribute.  Is there something else I can/should do in order to deprecate
a Mojo parameter?

-Dan

Re: Preserving backwards compatibility?

by brettporter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

That works.

On 26/11/2007, at 5:14 PM, Dan Fabulich wrote:

>
> In revisions 598168 and 598171 I added support for an "aggregate"  
> mode to the surefire-report plugin.  In this mode, the plugin will  
> aggregate XML test results from multiple directories, just like the  
> javadoc and jxr plugins.
>
> In 2.3, surefire-report takes exactly one "reportDirectory".  In  
> 2.4, the plugin now accepts an array of "reportDirectories".
>
> In order to maintain backwards compatibility, I continued to accept  
> the old "reportDirectory" property, marking it with the  
> "@deprecated" javadoc attribute.  Is there something else I can/
> should do in order to deprecate a Mojo parameter?
>
> -Dan

--
Brett Porter - brett@...
Blog: http://www.devzuz.org/blogs/bporter/