[
https://issues.apache.org/jira/browse/BOOKKEEPER-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397042#comment-13397042
]
Mridul Muralidharan commented on BOOKKEEPER-292:
------------------------------------------------
This fix breaks the build.
In particular, it introduces dependency issues :
$ mvn -DskipTests=true clean
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='org.apache.bookkeeper:bookkeeper-server'}' and
'Vertex{label='org.apache.bookkeeper:bookkeeper-server-compat400'}' introduces
to cycle in the graph org.apache.bookkeeper:bookkeeper-server-compat400 -->
org.apache.bookkeeper:bookkeeper-server -->
org.apache.bookkeeper:bookkeeper-server-compat400
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jun 20 01:54:37 IST 2012
[INFO] Final Memory: 3M/26M
[INFO] ------------------------------------------------------------------------
> Test backward compatibility automatically between versions.
> -----------------------------------------------------------
>
> Key: BOOKKEEPER-292
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-292
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-292.diff, BOOKKEEPER-292.diff
>
>
> At the moment, backward compatibility between 4.1.0 and 4.0.0 can only be
> tested manually. This JIRA is the set up the code base, so we can validate
> behaviour between versions automatically, and spot if a change breaks
> functionallity between versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
