Re: [Fwd: CVS update: MODIFIED: compilation, prj40_prototype ...]

Ok, fair enough. I just looked at the constant at the wrong time then.

As for using using unpublished settings format: I am probably using many 
more things like this. My impression was that the message I got from 
projects and java teams was: start using our settings formats (even 
create a project and copy settings from .project file into your 
template), we plan to document it later. I think I should go thru this 
and ask check if every single thing I am using is documented and files 
issues. I will try to do this.

diky,
-pavel

Jan Pokorsky wrote:
> I am sorry for difficulties but the code WAS broken. I revealed it 
> thanks to java xtests. The setting is registered in the 
> projects/compilation nature under the Build type configuration as 
> 'proj-comp-outputfolder'. It is also used in the Sample project and 
> compilation xtests. The change from 'proj-comp-outputfolder' to 
> 'proj-comp-outputFolder' was caused in all likelihood by accident as a 
> part of the fix of the issue #34939 (see 
> OutputFolderContextSupport.java, revision 1.1.2.10).
> 
> AFAIK the setting is not published anywhere in documentation so I did 
> not consider necessary to notify the fix ahead. If you need such an API, 
> please file a RFE for the projects/compilation module.
> 
> Jan
> 
> 
> Pavel Buzek wrote:
> 
>> Honzo,
>>
>> this integration caused an NPE in web module when you call Build 
>> Project (it's fixed now). I am using proj-comp-outputFolder in my 
>> template as AFAIK this is the only way to set the output folder for my 
>> build target declaratively. Is this attr recommended for use as an 
>> API? If so then any such change must be notified ahead.
>> It's also not clear where was the request for this change coming from. 
>> If it's not broken don't fix it :-)
>>
>> -pavel
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>