Have you tried latest WTP dev build?
http://download.eclipse.org/webtools/downloads/drops/R3.6.0/I-3.6.0-20140118023607


On Tue, Jan 21, 2014 at 8:29 PM, Norman Cohen <nhco...@google.com> wrote:

> Fred,
>
> Any update on this fix? Are you aware of any workarounds (e.g., obtaining
> a jar with the patch or somehow setting the environment so that the call on
> IModelProvider.getModelObject() in
> AbstractMergedModelProvider.getLastModificationTimeOfDDFile() returns a
> non-null EObject with a null eResource)?
>
>
> On Tue, Jan 7, 2014 at 3:50 AM, Fred Bricon <fbri...@gmail.com> wrote:
>
>> Hi,
>>
>> Bug 408327 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327> [1]
>> supposedly fixed last may is still showing its ugly face.
>>
>> The patch was applied the 28/05/2013 on both master[1] and the 3.5
>> branches[2]
>>
>> The Kepler SR1, Luna M4 and latest R build (wtp4x-R3.6.0-I:
>> I-3.6.0-20140102051318) all contain an
>> outdated org.eclipse.jst.jee_1.0.600.v201305131500.jar
>>
>> Looking at the git log on that plugin, the only explanation I can come up
>> with is the latest commit(s) was not included in any tags. But I'm not
>> familiar with WTP's build procedures so there may be another explanation.
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327
>> [2]
>> http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=865964f2ad5fdf209074cbe8b0db2dce91be19ce
>> [3]
>> http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?h=R3_5_maintenance&id=865964f2ad5fdf209074cbe8b0db2dce91be19ce
>> [4]
>> http://git.eclipse.org/c/jeetools/webtools.javaee.git/log/plugins/org.eclipse.jst.jee
>>
>> "Have you tried turning it off and on again" - The IT Crowd
>>
>>
>
>
> --
> Norman Cohen
> Cloud Platform developer tools
> Google NYC
> nhco...@google.com
> Google Voice: (253) 642-6436 (253-NHCOHEN)
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to