Community
Participate
Working Groups
I may be missing some key bit of knowledge, or perhaps, at some level, this is an eclipse executable limitation (if not bug) but since I've not really seen non-delimited commands used before, I wonder if that's too non-standard? Here's what I mean ... I've tried creating and ant script, to run the aggregator, launching from "eclipse" executable. Specifically <exec executable="${eclipseExecutable36}" dir="${basedir}" failonerror="true"> <arg value="aggregate" /> <arg value="-debug" /> <arg value="-nosplash" /> <arg line="-data ${eclipseWorkspace}" /> <arg value="--launcher.suppressErrors"/> <arg line="-vm ${JAVA_5_HOME}/jre/bin"/> <arg line="-application org.eclipse.b3.cli.headless" /> <arg line="--buildId ${buildId}"/> <arg line="${AGGREGATOR_APP_ARGS}" /> <arg line="${BUILDER_VM_ARGS}" /> </exec> No matter what I do, the 'aggregate' command simply gets combined with whatever comes before it. I'll attach log from above example, that shows it "attached" to the --startup jar line from eclipse executable. If I move it around, it just gets "attached" at the end of something else, and never recognized by the aggregator app as a command. Is there something I'm missing? Some important reason it was done this way? An obvious bug or change in behavior in eclipse executable launcher?
Created attachment 167647 [details] full "log" of attempthing to run this particular ant task
The ant executable task will just pass the arguments in the same order that they are given to it. The 'line' arguments will be parsed into pieces and the 'value' arguments are passed verbatim. The re-ordering that takes place comes from the launcher and from the looks of it, it is correct. The 'aggregate' command is indeed called. So I'm not sure I understand what you mean with "non-delimited commands" or what the issue is. The error you get is due to the missing --mirrorReferences option.
Created attachment 167659 [details] another example I was obviously confusing my self ... but, just so you know, here's another example where it doesn't "find" 'aggregator' after following a line argument that ended with the logURL value. So, still not sure why it works in some locations, and not others ... but ...
but, I have seen it work in some locations (after removing --mirrorReferences) ... so I guess its working as designed.
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. No change to assignee for resolved and verified bugs.]
