Is this different from the compat issue fixed by using:

<configuration>
   <useJql>true</useJql>

?

Gary

On Mon, Nov 19, 2012 at 2:59 PM, Benson Margulies <bimargul...@gmail.com>wrote:

> Atlassian made an incompatible change to JIRA that they have marked 'won't
> fix':
>
> https://jira.atlassian.com/browse/JRA-29152
>
> Unless they can provide some alternative, the maven-changes-plugin is
> essentially worthless for JIRA instances of that version or newer,
> which includes the ASF main JIRA instance. They say that they plan to
> include an alternative in 5.2; so once they release 5.2, and ASF JIRA
> runs it, someone can patch up the m-c-p to work with it. Until then,
> we are all out of luck.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to