On Fri, Jun 13, 2008 at 9:39 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Bernd Fondermann ha scritto: >> >> On Thu, Jun 5, 2008 at 10:05 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >>> >>> nodje ha scritto: >>>> >>>> hey thanks >>>> >>>> I haven't open the documentation yet but thanks to Maven I have been >>>> able >>>> to compile the whole stuff. >>>> spring-integration wouldn't compile on it's own though. Some missing >>>> dependencies - or repository issue. >>> >>> I committed fix to poms yesterday, please try again with the latest >>> version. >> >> We are going long ways to maintain two build tools. I'd suggest we >> better point our users to the ant build and not turn people away early >> because they try to use maven and fail. >> >> Bernd > > If you look at the thread I already suggested him to use ANT but he decided > to use maven anyway. So I preferred to take the opportunity to fix the maven > build (we needed this action anyway for our website build). > > In my answer I never used the maven word and here is a quote from what I > suggested him: >> If you checkout the whole sources for trunk and run "ant" on the root >> it will build also the spring-deployment packages. > > Stefano
Yes, I know. I can read ;-) The point is: Having two build tools means, changing one build probably breaks the other one. We did not yet agree to maintain both (except for using maven for docs). The nightly build for example does not check the maven build. But having a broken build is bad for those innocent folks trying to use it. But there is another aspect. AFAIK, maintaining a complete maven build is not consensus in the team. This thing appears to be sneaking in. It is better to try to have an open discussion about that instead of silently acting upon it. That's also why I bring it up. I think it is vital for Apache projects to not depend on remote repositories to be available to make builds work and to have all dependend libraries in the project's repository. Otherwise, some day, old builds will no longer work because of missing dependencies. Apart from that, I do not prefer ant over maven. Or to put it the other way round: I am +1 to switch to maven if I can do svn co $TRUNK <switch off network access> rm -rf $LOCAL_MAVEN_REPOSITORY mvn => build succeeds <optional: switch on network access :-) > Bernd > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
