More than one build tools is not way to go, I believe everyone agrees on that, and that it's not an issue.
Have you guys at least considered making a switch to a build tool that knows to produce maven artifacts (or enhancing exiting one to take care of that)? E.g. ant+ivy, gradle, maven itself. IMO making a switch to a modern build tool or enhancing existing one to produce maven artifacts at the moment is out of best interest for any open source project including this one, it will be out of benefit for projec users/contributors, developers, and project as a whole: - official project binaries will (continue to) be available to as large as possible user base so you'll get more potential testers/bug reporters, and more potential contributors, and more potential commercial/paying customers which will raise project quality, bring new ideas, and finance future development - modern build tools have declarative dependency management so it will be easier to develop and contribute, at least one won't have to wait for dependency libs to get downloaded together with sources every time project is checked out and you will not have to manually download new/updated 3rd party dependencies, just change build script/metadata - modern build tools try to be and mostly are non intrusive, and promote good proven solutions like standard project structure/layout so it's easier to get started and productive on such projects compared to projects with custom layout; - modern build tools are better integrated with current development infrastructure tools, like IDEs, and continuous integration servers. This switch would also make it easier to maintain project metadata, to keep metadata DRY, so that publishing Maven artifacts even if decided not to be part of main release process, can be done with not much effort and enough credibility. If who cares about project maven artifact consumers regardless of size of that community attitude is accepted and official project stand, and project community size is not considered as project asset, I don't understand why project is being published under open source license. Regards, Stevo. On Tue, Jan 18, 2011 at 11:50 AM, Robert Muir <rcm...@gmail.com> wrote: > On Tue, Jan 18, 2011 at 5:29 AM, Hardy Ferentschik <s...@ferentschik.de> > wrote: > >> It also means that someone outside the dev community will at some stage >> create some >> pom files and upload the artifact to a (semi-) public repository. > > This sounds great! this is how open source works, those who care about > it, will make it happen! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
