Hi Igor, going back to Maven is no option at the moment. We didn't build/chose to use Buildr for fun but because of the severe pain we had with Maven. Even when assuming the maven uncertainty principle is solved and Maven has improved in general, there are several features in our build that Maven simply cannot provide and which would take lots of efforts to rebuild it. To name a few its the acceptance testing in axis2-war, which supports testing against multiple databases or the creation of SQL DDLs for a whole bunch of databases. When we switched to Buildr we could cut down the build script size from some thousands of lines of XML code to some hundreds of Ruby code. As a side effect, the build became twice as fast and we had the ability to escape to plain ruby for things that the build system did not support out of the box.
A better and more feasible solution is to improve the build instructions and our documentation to make it less hassle for you. What difficulties did you exactly experience? Best, Tammo On Wed, Mar 11, 2015 at 5:59 PM, Igor Vorobiov <igorvorobio...@gmail.com> wrote: > I agree about difficulties related to using Apache Buildr for ODE build. > I've noticed that maven build is deprecated and not maintained anymore: > > > https://issues.apache.org/jira/browse/ODE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353619#comment-14353619 > It would be good to have compatibility with maven build if it is possible. > > > > -- > View this message in context: > http://apache-ode.996305.n3.nabble.com/Build-with-Java-8-tp17530p17531.html > Sent from the Apache Ode Dev mailing list archive at Nabble.com. > -- Tammo van Lessen - http://www.taval.de
