Maybe there is something else going on then, but without this, class
reloading wouldn't work for me ... Every change to a framework caused
Eclipse to require a restart.
ms
On Nov 19, 2007, at 2:36 PM, Anjo Krank wrote:
> This is maybe not so good. Harald at some time had problems because
> they were discovering resources via bundleForClass and that broke
> with this... and the class should end up in the build folder after
> the incremental build had run it's course anyway.
>
> Cheers, Anjo
>
> Am 19.11.2007 um 20:28 schrieb mschra..bjectstyle.org:
>
>> Author: mschrag
>> Date: 2007-11-19 14:28:03 -0500 (Mon, 19 Nov 2007)
>> New Revision: 4655
>>
>> Modified:
>> trunk/woproject/wolips/core/plugins/
>> org.objectstyle.wolips.launching/java/org/objectstyle/wolips/
>> launching/classpath/WORuntimeClasspathProvider.java
>> Log:
>> put bin folder in the cp so we get class reloading
>>
>> Modified: trunk/woproject/wolips/core/plugins/
>> org.objectstyle.wolips.launching/java/org/objectstyle/wolips/
>> launching/classpath/WORuntimeClasspathProvider.java
>> ===================================================================
>> --- trunk/woproject/wolips/core/plugins/
>> org.objectstyle.wolips.launching/java/org/objectstyle/wolips/
>> launching/classpath/WORuntimeClasspathProvider.java 2007-11-19
>> 16:54:29 UTC (rev 4654)
>> +++ trunk/woproject/wolips/core/plugins/
>> org.objectstyle.wolips.launching/java/org/objectstyle/wolips/
>> launching/classpath/WORuntimeClasspathProvider.java 2007-11-19
>> 19:28:03 UTC (rev 4655)
>>.. -136,6 +136,7 @@
>> // a project and add that instead of the bin folder ...
>> if (projectArchive != null) {
>> if (!allProjectArchiveEntries.contains(projectArchive)) {
>> + pendingResult.add(entry);
>> IRuntimeClasspathEntry resolvedEntry =
>> JavaRuntime.newArchiveRuntimeClasspathEntry(projectArchive);
>> pendingResult.add(resolvedEntry);
>> allProjectArchiveEntries.add(projectArchive);
>>
>
This archive was generated by hypermail 2.0.0 : Mon Nov 19 2007 - 15:52:41 EST