On 30 November 2012 13:40, Radim Kolar <h...@filez.com> wrote: > > inline ant scripts >>> >>> =0. Ant's versioning is stricter; you can pull down the exact Jar >>> versions, >>> and some of us in the Ant team worked very hard to get it going >>> everywhere. >>> You don't gain anything by going to .py >>> >> there are sh scripts inside maven ant plugin stuff >
Which is because there are some things you can't do in Java -run rpmbuild to pick up file permissions and hanging symlinks that only become valid on deployment. The reason Ant is used to start them is Maven views trying to run native scripts as a forbidden action - probably popping up some patronising text "you are trying to run a shell script, please look at maven.apache.org/wiki/whymavenwontletyoudothings/ to understand this; they also view building RPMs as not something to encourage either. (but we digress into an ant vs maven argument. I do actually appreciate the consistent target naming across projects and the ability for the IDE to set up structure, it's just the entire underlying architecture and implementation that I dislike)
