Here is my situation. I’ve spent the past three months primarily engaged in two efforts:
- Getting up to speed on gradle
- Developing plugins for building rpm files, our team’s chosen deployment mode
Now this is being rolled out to the wider team. Although I do some web development, it’s not a major use of time for me, it is quite sufficient to make a tweak here, a tweak there commit it to source control, build my war-containing rpm on the server and deploy it and test.
Others on my team do much more web development. I am starting to get complaints because they miss the level of Eclipse tooling support they are used to having with Maven. They are used to deploying a Maven project onto a local Tomcat server within Eclipse.
It is not clear how you do all of this with Buildship. The apps won’t deploy. Maybe once it does, once it doesn’t. If things go bad, and they sometimes do, you might have to blow away your Eclipse project, and then reimport a gradle project from a git repo. And deal once again with all the .project .classpath, .settings, etc.
I’ve raised a number of issues about them:
These issues are costing lots of their time and also mine as I’m being looked at to help solve them.
As one of my colleagues put it:
with Maven projects, it all just worked beautifully, didn’t need to be an Eclipse guru … I’m so far behind the expected delivery schedule, and it’s mostly due to this stuff
And I can’t argue with him.
The point of this is not to whine. I understand where gradle is coming from, and the prodigious efforts that have gone into it thus far, and I find it amazingly good. Maven has a big head start, and I’m fully confident that in a couple years, if not a few months, things will be much better than they are now, good enough to satisfy my colleagues. I am not underestimating the difficulty of collaborating within Eclipse, with Eclipse bugs, etc.
But it’s still an objective fact that in May, 2016 gradle-eclipse integration is not where it needs to be.
And so, I’m looking for a temporary way of having the best of both worlds:
Has anyone tried having projects with BOTH a pom.xml and build.gradle in them? They could be loaded into Eclipse as Maven projects, developed within Eclipse, code checked in, and built with gradle on a server.