Re: Javac settings

Jan Rojcek wrote:
> 
>> 3.) You have not answered yet my previous mail where I asked how to 
>> handle output folder. Is it possible to customize compiled classes' 
>> output folder just via Additional Javac Options (-d option)?
>>
> 
> Sorry. The output directory is defined by build target, right? As a 
> configuration is used with a different build targets, it would just 
> confuse users why she is asked to define it here (I hope I understand 
> configurations well, though). In case the user writes the -d option then 
> we should just use it.
>
The user should *never* enter paths into text fields if we can avoid it. 
An absolute path makes the project non-transferable to other machines.

>> 4.) How to solve conflicts between Additional Javac Options and ui 
>> components?
> 
> The written options take precedence over the gui components.
> 
Well. You may cross the implementation design here - it requires to 
provide different option bean for configuration (ui) purposes and a 
different bean for the work itself: the "worker" one will contain merge 
of the free text + GUI.
Otherwise, supported options recognized in the hand-written text would 
just disappear and change the GUI ones.

The other possibility for implementation is do the merge/override in 
individual compiler's implementation; probably the best approach anyway.

-Svata