Community
Participate
Working Groups
As far as I can see, from docs and google searching, the tycho-eclipserun-plugin provides only <appArgLine>one big long line</appArgLine>. It seems better to follow the pattern I recently learned about with the compiler configuration. I forget what original was called, which took a "line" as the argument, but was told it was deprecated and I recently changed to: <compilerArgs> <args>${code.ignoredWarnings}</args> <args>-verbose</args> <args>-inlineJSR</args> <args>-enableJavadoc</args> <args>-encoding</args> <args>${project.build.sourceEncoding}</args> ... It would be best, IMHO, to deprecate <appArgLine> and provide, say <applicationsArgs> which took <args> as "children". This is better since it is less "breakable" due to formating changes, plus, on most OSs ... well, on Linux anyway :) ... it's "smart" about "args" it is passed, and (if done right?) You can pass <args>several words as one argument</args> without a lot of complicated escaping (that can vary from OS to OS).
(In reply to David Williams from comment #0) > As far as I can see, from docs and google searching, the > tycho-eclipserun-plugin provides only <appArgLine>one big long > line</appArgLine>. +1 I've got bitten several times already by the m2e POM Editor automatically warping a 200+ characters <appArgLine>, since line breaks therein cause the tycho-eclipserun-plugin to fail during the build.
Gerrit change https://git.eclipse.org/r/52215 was merged to [master]. Commit: http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/commit/?id=9d1974347caa19ca2b1804e7ce7bb8aca1a32837
The old parameter "appArgLine" is now deprecated but still works. The new one is called "applicationsArgs". Example: <build> <plugins> <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-eclipserun-plugin</artifactId> <version>{tycho-version}</version> <configuration> <applicationsArgs> <args>-buildfile</args> <args>build-test.xml</args> </applicationsArgs> </configuration> </plugin> </plugins> </build>