I'm well aware that this is not a great practice but this is the only pragmatic solution to trick the desired mojos into doing what I want. Using bash scripts would end up being worst since then I would have to have such a script into every level where the build can be fired from. Anyway, thanks for your insights.
Pascal On 2012-08-23, at 11:42 AM, John Kramer wrote: > > > > > >> Am 23.08.2012 14:56, schrieb Pascal Rapicault: >>> Hi, >>> >>> I would like to know if there is a way to have a plugin be executed >>> right at the end of the build no matter what. The situation I have is >>> as follow. Early on in the build I rename a file from a.txt.off to >>> a.txt and at the end I rename it back such that no problems are being >>> caused for subsequent builds. This works great when the module build >>> is executed in its entirety, however when it fails part way through, >>> then the file is not renamed and subsequent build fails. Therefore my >>> question, is there a way to enforce the execution of a plugin no >>> matter what. >> >> Hi, >> >> ensure that you REALLY want to change files in your "src" folder during >> maven build. This looks like a bad practice. Always "do things" in the >> target folder. It is there to provide clean builds. >> > > I concur. If you ABSOLUTELY need to modify something in your src folder, > DON'T DO IT AS PART OF A MAVEN BUILD. That violates the pattern that > maven uses. Instead, think about doing it as part of a larger process > (i.e. do it as part of a bash script, or something else). > > Or better yet, work in your target folder. > > > John Kramer > email: [email protected] > mobile: 314.435.2370 > twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech> > 0xCAFEBABE00000032 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
