[dtp-dev] Preparation for the 12/9 iteration build

[jograham@xxxxxxxxxx]

I'd like to check assumptions for the 12/9 iteration build:

1) Plug-ins included:

org.eclipse.datatools.connectivity
org.eclipse.datatools.connectivity.db.derby
org.eclipse.datatools.connectivity.db.generic
org.eclipse.datatools.connectivity.oda
org.eclipse.datatools.connectivity.oda.flatfile
org.eclipse.datatools.connectivity.ui
org.eclipse.datatools.connectivity.ui.dse
org.eclipse.datatools.modelbase.dbdefinition
org.eclipse.datatools.modelbase.sql
org.eclipse.datatools.modelbase.sql.edit
org.eclipse.datatools.sqltools.editor.core
org.eclipse.datatools.sqltools.result

The CVS head for this plug-in set currently builds without error in Eclipse
3.2M3. Does anyone want to add or remove plug-ins from this list?

Next, there is a problem with Eclipse 3.1: The plug-in
"org.eclipse.datatools.connectivity.compatibility" does not seem to be used
by DSE, so the only way I can DSE to build in 3.1 is to include
"...navigator.common" and "....navigator.views" (both CVS head) and
"...dse" from CVS tag DTP_M1. Also, "org.eclipse.datatools.connectivity.ui"
CVS head does not build in 3.1, so I need to use the DTP_M1 tag there as
well.

Ideally, we'd have one build for Eclipse 3.1 and 3.2, but it is easy to
imagine why we might not be able to accomplish this. Will it be necessary
to split the build, or can these issues be addressed for 12/9? Note that
going out with the DTP_M1 tag for "...ui" and DSE could work (since the
"navigator.common" and "navigator.views" plug-ins are tolerated in 3.2),
but any code changes made past DTP_M1 will not be reflected.

2) Each plug-in now includes a source code zip and JavaDoc where
appropriate.

3) With the exception of the ODA components, I have updated the version
number to "0.7.0". Changes to the manifest files will be made in CVS to
reflect this.

4) The download zip will have the standard Eclipse folder structure,
including a "features" folder, even though it is empty at the moment.

5) The name of the download file will follow the Eclipse convention. So, on
Friday we will have "dtp-SDK-0.7M2-I120905.zip"

The "SDK" indicates source code and JavaDoc included, "M2" is the milestone
this build is working toward, and "I120905" indicates an iteration build
for the given date stamp.


Any thoughts or comments about these points?

Regards,
John Graham
Eclipse Data Tools Platform PMC
Staff Software Engineer
Sybase, Inc.