Part of the problem, for me, is learning what the issues are with Maven that maven developers will find problematic.
One of the problems we're going to have is that the Maven central repository simply cannot provide the proprietary building materials for the connectors that need them, for instance Livelink and Documentum. These materials will always need to be pushed into a local repository, and it is also true that conditional compilation will also always be required, since any one builder will not have access to all proprietary libraries. Anyone have a good Maven solution to that? Karl On Wed, Sep 21, 2011 at 3:52 AM, Alex Ott <alex...@gmail.com> wrote: > Hello > > On Wed, Sep 21, 2011 at 9:43 AM, Tommaso Teofili > <tommaso.teof...@gmail.com> wrote: >>> (2) I'm not sure it is reasonable to go with one build system over >>> another. Lucene/Solr has been having this battle for years. I >>> thought we might just learn from that experience and try to be more >>> flexible. There are excellent technical reasons to have each - for >>> instance, building Debian packages works much better with Ant, and >>> Eclipse works much better with Maven. >>> >> >> I don't like "wars" as well about which one *is* better, maybe it's just a >> matter of use case and personal preferences. >> However I like what you say about trying to be more flexible so I am +1 to >> your position. >> I have some experience with Maven so let me know if you need my help in >> tweaking that part of the build. > > I also have some experience with Maven, and I'm interested in MCF's > development, so I can try to fix some problems. The first thing, that > should be achieved - building with Maven out of box, without manual > work (or at least with minimum of it). > > -- > With best wishes, Alex Ott > http://alexott.net/ > Tiwtter: alexott_en (English), alexott (Russian) > Skype: alex.ott >
