On Jun 22, 2011, at 10:08 AM, Allen Wittenauer wrote:
>
> On Jun 21, 2011, at 2:02 PM, Harsh J wrote:
>>>>
>>>> If your jar does not contain code changes that need to get transmitted
>>>> every time, you can consider placing them on the JT/TT classpaths
>>>
>>> ... which means you get to bounce your system every time you change
>>> code.
>>
>> Its ugly, but if the jar filename remains the same there shouldn't
>> need to be any bouncing. Doable if there's no activity at replacement
>> point of time?
>
> I have yet to find a jar file that never ever changes.
(I suppose the exception to this rule is all the java code at places
like NASA, JPL, etc involved with the space program. But that's totally
cheating!)
