Community
Participate
Working Groups
I've cloned all of the Data Tools Git repositories but cannot find the source for the org.eclipse.datatools.intro bundle. I was eventually able to locate a JAR file in the org.eclipse.datatools.doc repository: $ grep "DTP_overview\.xml" -R . Binary file ./org.eclipse.datatools.doc/packaged_jars/org.eclipse.datatools.intro_1.7.0.v201005281800.jar matches Similiarly, I can't find the source for these JARs: org.eclipse.datatools.connectivity.doc.user.contexts_1.7.0.20090521092446.jar org.eclipse.datatools.sqltools.doc.user.contexts_1.7.0.20090521092446.jar Is this intentional? I assume that this source must have just gotten lost or somehow missed when the project migrated to Git. It would probably be better to recover the source if we can, but in the worse case, the contents of the JAR are effectively source. I'd really like to see this source in Git. I have some patches that I'd like to propose... I'm marking this as critical because the project source really needs to be managed in a manner that makes it open for contribution.
Yep. I saw that myself when working on getting a DTP build going. Had to make special accommodations for these pre-built jars. Had it on my todo list to bring up, so I am glad that you got to it before I did.
I'm assuming that it is in the CVS archive. I've marked this as a 'hackathon' bug and will try to use some of my time during the hackathon to either locate the source or reverse-engineer it (I'm hopeful that this is possible since it looks like documentation).
I found what I think is the source in the old CVS repository. /cvsroot/datatools/org.eclipse.datatools.build/templates/org.eclipse.datatools.intro_1.0.0.200612151 CVS is read-only and there's no outward server access. It should be relatively easy to extract it using RCS. Ideally, we should try to preserve the history. I'm going to assume that--despite the name of the directory--since this directory has the same structure as the JAR file, that some build script knows how to turn this into the JAR. Sorting out that, I think, will be the challenging part.
If you extract the source from CVS, I will figure out how to wire it into the build.
