Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329257

Summary:	JET should generate code that is compatible with the JVM's hot code replacement restrictions
Product:	z_Archived	Reporter:	Paul Elder <pelder.eclipse>
Component:	Jet	Assignee:	Paul Elder <pelder.eclipse>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	pelder.eclipse
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Paul Elder

2010-11-02 09:56:15 EDT

When changing a JET template in a workbench it is possible to make a change that will result in code that will fail a hot code replacement in the second workbench.

Use Case:
Start first workbench containing JET templates that generates code used in a second workbench.

It is possible that the template change generates code that is incompatible with the hot code replacement of the JVM.

In previous versions of JET, such hot code replacement failures were much less frequent. Starting with JET 0.9.x, replacement failures occur anytime a tag moves in the file (either shifts in its existing line or changes its line number).

Comment 1 Paul Elder

2011-01-27 14:22:50 EST

Fixed in JET 1.1.1 (Helios SR2)

Support a new property in .settings/org.eclipse.jet.prefs:

org.eclipse.jet.hcrFriendly = true

When set to true, the Java code generated for a template is invariant with respect to member fields (which is the thing HCR has problems with).

No UI is yet available to set this value - you must edit the above file by hand. UI may be produced in the Indigo.