[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-debug-dev] debug.core jar files
|
>>>>> "Doug" == Douglas Schaefer <dschaefe@xxxxxxxxxx> writes:
Doug> I'm trying to get the builds going again and noticed a new jar file in
Doug> debug.core, cdi.jar. There's no problem adding a new jar file, however,
Doug> there are classes in the cdi source folder that still refer to the src
Doug> source folder and, thus, fail to build.
I meant to mention that I ran into this. I worked around it with the
appended patch -- probably bogus.
Now I wonder whether I really have the 2.0 sources. I suspect the
releng code that checks out the map files again fetched HEAD and not
CDT_2_0.
It would be really convenient for me if the map files were updated to
refer to a release tag, and then the releng plugin itself were tagged
with that same tag. Then, I think, fetching a particular release
would be very simple: check out the releng plugin with a given tag,
then run the fetch target to get the correct versions of all the
plugins.
What do you think?
Tom
--- org.eclipse.cdt.releng/results/plugins/org.eclipse.cdt.debug.core/build.properties.~1~ 2004-07-02 13:30:18.000000000 -0600
+++ org.eclipse.cdt.releng/results/plugins/org.eclipse.cdt.debug.core/build.properties 2004-07-12 17:14:37.000000000 -0600
@@ -23,5 +23,5 @@
org.eclipse.cdt.debug.core.cdi.model.*
src.includes = schema/
jars.compile.order = cdi.jar
-source.cdi.jar = cdi/
+source.cdi.jar = cdi, src
output.cdi.jar = bin/