I’m getting more and more into the Java World at the moment. Switching from pure Domino to pure Java. Outside of Domino, there’s a lot about manageing dependencies. The freedom of choice is paid by work to beat different runtimes.
\nLooking for a decent tool to help managing dependencies I came across Ant, Maven and Gradle.
\nAnt I new from the past. It’s ok but seems to be a lot of code to write and it’s XML…
\nMaven? Seems that I’m not smart enough.
\nI was not able to setup a working multi project setup without installing my sub projects in a repository. And it’s XML too.
\nGradle, the youngest among these three, groovy based. After reading through some tutorials, and combing through stackoverflow I was able to setup my multi-project build,
\nwith integratopm into my eclipse environment.<\/p>\n
Even a Vaadin client is compiling with the right plugin. So I was not forced to use the Vaadin eclipse plugin at all. One thing I was not happy, the Vaadin plugin compiles some JavaDoc and Sources into my final EAR.<\/p>\n
Step 1: Remove the JavaDoc and Sources from the deployment descriptor<\/p>\n
\r\ndeploymentDescriptor{\r\n....\r\nwithXml {\r\ndef javaDocNode = asNode().module.find { it.ejb.text().contains('javadoc.jar') }\r\nif (javaDocNode) {\r\nasNode().remove( javaDocNode )\r\n}\r\ndef sourceNode = asNode().module.find{it.ejb.text().contains('sources.jar') }\r\nif (sourceNode) {\r\nasNode().remove(sourceNode)\r\n}\r\n}\r\n}\r\n<\/pre>\n <\/p>\n
Step 2: Removing the actual Jar’s from the EAR<\/p>\n