Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Ouch: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=41353" rel="noreferrer">7-years bug</a>, asking for running configuration template, precisely for that kind or reason.</p> <p><a href="http://dev.eclipse.org/newslists/news.eclipse.tools.jdt/msg07770.html" rel="noreferrer">This thread</a> proposes an interesting workaround, based on duplicating a fake configuration based on string substitution:</p> <blockquote> <ol> <li>You can define variables in <code>Window-&gt;Preferences-&gt;Run/Debug-&gt;String Substitution</code>. For example you can define a <code>projectName_log4j</code> variable with the correct <code>-Dlog4j.configuration=...</code> value.<br> In a run configuration you can use <code>${projectName_log4j}</code> and you don't have to remember the real value.</li> <li>You can define a project-specific "empty" run configuration.<br> Set the project and the arguments fields in this configuration but not the main class. If you have to create a new run configuration for this project select this one and use 'Duplicate' from its popup-menu to copy this configuration.<br> You have to simply set the main class and the program arguments.</li> </ol> <p>Also you can combine both solutions: use a variable and define an "empty" run configuration which use this variable. The great advantage in this case is when you begin to use a different log4j config file you have to change only the variable declaration.</p> </blockquote> <p>Not ideal, but it may alleviate your process.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload