On Apr 10, 2014, at 4:12 PM, Rafał Krupiński <[email protected]> wrote:
> Dnia 2014-04-10, czw o godzinie 14:40 -0500, Gregg Wonderly pisze: > >> Maybe you can explain at this point. Is the problem that you can’t build, >> at all, to test your changes? Is this because you don’t have ANT? > > Are you, by any chance, being sarcastic? I am not trying to be sarcastic, I am trying to find out what keeps you from editing River files to make changes you want, testing those changes and submitting them. One of the chief things for me, is the question of how does a “build” system cause a “source tree” to be uneditable, untestable etc. There are very few things about River’s “jars” that are cast in stone. You can pretty much create two jars, one from services and one from proxies and be done. The multiple *-dl.jar files are a separation of “function” that might reduce overall downloads, but in the end, the overhead of multiple http transactions is probably much larger than the overhead of downloading all the proxies in a single jar. I know that it is “work” to create a build system if you need something different than what something comes distributed with. But, that’s the question here. If the build system is keeping people from contributing, then why isn’t there a “github” distribution of the appropriate tooling that everyone can try and see how much better it is? I am not trying to push back and be sarcastic. I am trying to be serious about what the real problem is. I am one of those developers who will only waste/spend so much time fighting with something before I either throw it away, or roll my own so that I know what is going on and don’t waste my time with lack of transparency that keeps me from understanding how my software is actually working. > >> It seems it’s because you don’t know how to use the ANT build system, >> which I can understand. But also, you need to understand that there are >> people who have no idea how to use Maven either. >> >> So, overall, how can we simplify things if there are always new and >> different build tools/standards that some people know and others don’t? > > Is learning a new tool the problem or how would the migration address > the problem of lack of contributions and new committers? Learning a new tool is the question at hand. If you find Maven to be your build tool of choice, then I think you’ve already decided to learn a new tool. If you don’t know how to use ant to build with the build mechanism that exists, then that creates a problem. If that is THE PROBLEM for everyone, then that’s what we need to understand and remedy it would seem. Gregg > Regards, > Rafał >
