Iburong wrote:My two cents:
I´ve been working for almost a decade as Java Enterprise developer, and I hate when I´ve to work in something without Maven. Ant can be easy to work with only if people use standard solutions. And they never do. Yes, pom making and mavenizing are not for the faint of heart, but neither is bloated ant configuration.
That said, I find that LeJOS ant files are simple and good configured. And it´s not a good idea to force a building solution upon developers if they are not comfortable with it. I´ve lost countless hours with configurations I did not really understand myself, instead of working on my real problems, so I don´t want the great LeJOS team to lose time and effort on these things if they are not badly needed. Maybe when the project is a stable release they will want to thinker with these new ways of configuring the project if they fancy them.
Of course, I´d prefer not to touch anymore an ant file, I´ve developed some kind of phobia to them But LeJOS is so awesome I´ll try to overcome those fears Besides, it seems some people on the forums are working with gradle and maven, see the Scratch 2.0 EV3 project, so it´s possible to use them with LeJOS without making them mandatory. Maybe some more examples projects with gradle would be nice?
For me, the ideal would be some way of making the two aproaches to work well together in the same project, but it can get messy to merge and to understand, maybe it´s better to have a normal ant release and a maven-gradle one, better suited for more complicated projects with dependency trees and the like. But the extra work could be too much for the real problems it solves. Maybe the LeJOS team should concentrate in making their solution as good as they can, and then the maven-gradle people could integrate their tech with other third party libraries for a more complex ecosystem.
But, as I said in the first place, those are only my two cents
Users browsing this forum: No registered users and 1 guest