Was answering on the phone on my previous mail.
Being a bit more speculative: it depends on what you do, but if I try to
guess:
you might have something that stores resolved props ('${project.version} in
some of your code).If so, you want to avoid that kind of manipulation in the sources. Prefer filtering properties file in src/main/resources and load it at runtime, that's the standard way to go. And going the standard way with Maven will always pay off later. Cheers 2013/2/19 Baptiste MATHUS <[email protected]> > Hi, > Which kind of updates are you doing exactly? > As a general rule, it'd be better to not touch files under the src > directories. > > Cheers > Le 19 févr. 2013 11:04, "Richard Vowles" <[email protected]> > a écrit : > > Is there any way to add files that get committed along with the prepare >> phase? >> >> I need a fully realized pom which the prepare-with-pom doesn't give me >> because of bugs in Aether, and our team uses Grails - which updates two >> files at release time to keep in sync with the pom version. >> >> I can't see any method of adding items to get committed in the release >> goals (not new items, but updated ones). >> >> Anyone got any ideas? >> >> Ta >> Richard >> >> -- >> --- >> Richard Vowles, >> Grails, Groovy, Java, Javascript, AngularJS >> Consistency is the last refuge of the unimaginative - Oscar Wilde >> ph: +64275467747, google+:http://rvowl.es/UX8Bmq >> podcast: http://www.illegalargument.com >> > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
