On 4 Jun 2015, at 14:19, Sander Verhagen wrote: > Hi group, > > > I'm toying with ideas to clean up a bunch of build configuration that we > have. There's some duplication going on, and I could push that into the > parent project. But since composition over inheritance is a good approach in > general, I'm thinking about using the Tiles Maven Plugin to do the same to my > build. I've played with it a long time
Thanks for the reminder - I have a bunch of reviews in the gerrit queue to fix the fact that the current release is kinda broken. Work has been keeping me hell busy lately. The incoming/pending patches fix a whole raft of issues I found with tiles in using them daily at work - the biggest being that I now disallow a tile being defined in a parent pom - forcing you to put them in the children ( solves issues with -pl etc. ) but currently gives me a maven warning about duplicate dependencies ( due to some mangling we do ). Ideally native composition would be far better than tiles, but that requires POM format changes. > So: are tiles still the way to go? (If they ever were) Tiles ( as they are ) do pose some interesting quirks and limitations esp. if you're already using a custom lifecycle ( we had to stop using `<packaging>bundle</packaging>` for our OSGi tiles in favour of the tile overriding the default jar plugin execution. And we can't seem to use release information in a tile ( I should remove that from the webpage actually since it looks like it won't actually work ). Mark -- Mark Derricutt http://www.theoryinpractice.net http://www.chaliceofblood.net http://plus.google.com/+MarkDerricutt http://twitter.com/talios http://facebook.com/mderricutt
signature.asc
Description: OpenPGP digital signature
