FYI, you may not have noticed it, but it's actually also adding the filtered source to the source folders usable by other classes. It's more "different" than "less" ;-). (Btw, templating actually uses part of the filtering subsystem provided by the resource plugin).
Cheers 2013/6/18 Arnaud bourree <[email protected]> > Yes, that's explain why that looks resources:copy-resources with less > functionality > > > 2013/6/18 Stephen Connolly <[email protected]> > > > Don't use it for that use case. That goal's use case is templating java > > code > > > > > > On 18 June 2013 16:05, Arnaud bourree <[email protected]> wrote: > > > > > Hi, > > > > > > OK, I don't used templating:filter-sources for this original goal: > Java. > > > My use case is to run shUnit2 test scripts to validate Bash script. > > > I've make context directory tree in src/test. > > > Now I'd like to copy contexts and script to validate in target/ > > > My SCM override execution flag, so when copying script, I need to force > > it > > > up: shUnit2 looks to request it > > > > > > Regards, > > > > > > Arnaud. > > > > > > > > > > > > 2013/6/18 Baptiste MATHUS <[email protected]> > > > > > > > Hi, > > > > templating:filter-sources copies things from src/main/java-templates > > AND > > > > adds it as a *source* directory (like java code, or so). > > > > Is this what you expect? > > > > > > > > Btw, as filtering generally just copies things from one place to > > > another, I > > > > suppose you should just set the corresponding chmod+x on your > original > > > > scripts? > > > > > > > > Cheers > > > > > > > > > > > > 2013/6/18 Arnaud bourree <[email protected]> > > > > > > > > > Hello, > > > > > > > > > > I'm looking at templating:filter-sources which look like > > > > > resources:copy-resources. > > > > > > > > > > I'd like to chmod +x copied scripts to run shunit2 against them. > > > > > > > > > > Does anyone know to do it without ant-run? > > > > > > > > > > Regards, > > > > > > > > > > Arnaud. > > > > > > > > > > > > > > >
