On Fri, 16 Jul 2010 10:34:22 +0200, Andreas Hartmann <andr...@apache.org> wrote: > Am 16.07.10 09:55, schrieb Vik Tara: >> On 07/16/2010 08:53 AM, Vik Tara wrote: >>>> >>>> WDYT ? >>> >>> >>> Makes sense. We could do something very quick and dirty :), as maven >>> can just call ant tasks. >>> >>> So as a first step perhaps just make lenya build from maven by calling >>> the exsiting ant tasks - and then replace them one by one? >>> >>> This way everything will continue to work ok. >> >> A pause for thought though... >> >> Should we do this right now - or should we do it in the future lenya >> version.
If we postpone all changes to the next version, so many changes to do, that none will be done. We have to move thinks step by step, with short cycles in order to : - don't break things - be able to revert - always have a compile trunk >> >> We may spend a fair bit of time doing this now - time which we could >> spend making new modules etc. > > I totally agree. Fundamental changes to the build process of a stable > app might be not such a good idea. There are many risks of breaking > things, Little changes that non break. We have to go forward, if nothing change, hard to prepare the future. > and you introduce a barrier for people who are familiar with the > current build process. IMO less and less people are not familiar in (maven usage increase more). And when good maven config, just 2 commands have to be know : mvn install & mvn tomcat:deploy... not a pita to learn... > >> What are the benefits of doing it now? > > * Use Maven's dependency mechanism for our module dependencies > * Get rid of our custom dependency management > * Reduce the size of the repository +1 > > But I agree that we should rather spend our limited resources on code > that creates a direct benefit for users. Sure direct (or short term) benefit have to be done, but architecture modification is a long term benefit that will cause great enhancement for users. Move or stay here ? Twice have risks, moving well could reduce them IMO. > > -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org For additional commands, e-mail: dev-h...@lenya.apache.org
