It's a good idea but not suitable for my case. If I'm calling sh, the real script would be an argument.In my case this would break the test cases for my command line argument validation tool.
Am 26.01.2011 um 21:03 schrieb Kathryn Huxtable: > That's a reasonable workaround. > > I think it's a reasonable thing to expect permissions on files to be > preserved. Consider this a +1 for a feature enhancement. > > -K > > On Jan 26, 2011, at 11:04 AM, Stephen Connolly wrote: > >> launch them with sh as the prefix on the cli, eg >> >> sh foo.sh >> >> and not >> >> foo.sh >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, random nonsense >> words and other nonsense are a direct result of using swype to type on the >> screen >> On 26 Jan 2011 15:36, "Oliver Schrenk" <oliver.schr...@gmail.com> wrote: >>> Hi, >>> >>> I have several shell scripts in src/test/resources that I try to call from >> within a JUnit test. The class under test is a wrapper arround >> plexus.utils.cli. >>> >>> When mvn copies the files to target/test-classes the executable bits are >> lost and the test fails due missing authorization. >>> >>> Any way to keep them? Or any other ideas? >>> >>> Best regards >>> Oliver Schrenk >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
