[dtp-pmc] DTP::Builds [Was: ODA plugin]

[jograham@xxxxxxxxxx]

All,

Sorry to be late getting back into this thread. I'd like to make a couple
of observations here and ask for feedback from the group and the PMC:

1. I have concerns about creating a simple DTP build at this point.
Currently we have a number of (essentially) final models in CVS, a bunch of
"sample" code, and some that is in transition. By "sample code" I mean the
non-model ports from WTP/rdb. By "in transition" I mean ODA at this point
and (some time really soon), the initial connectivity components from Rob.
These "in transition" components will need to be integrated with the other
DTP components and the samples will be replaced/augmented by DTP components
later. Based on our previous discussions, my belief is that everyone here
(and in DTP) understands and agrees to this (if not, then this would be a
really good time to speak up.  :-)  ). My concern is that people picking up
the build will not understand these distinctions, even if we go to pains to
document them in the downloads/build pages. I think it would be a
substantial disaster to introduce such confusion into the community, and
that we'd spend a lot of time going forward sorting this out and responding
to accusations that we "keep changing things." Given these considerations,
I'd like to suggest three possibilities:

    a. We do a build of Model Base only
    b. We do separate builds: Model Base and the rest. The download for
"the rest" is clearly explained to be samples/in transition.
    c. We build Model Base only and provide instructions on how to build
the rest. The instructions make clear the sample/transitional nature of the
components

I would prefer (a) as my first choice, then (c) and finally (b). Of course,
this does not preclude others (e.g. BIRT) from building directly from
DTP:CVS for their own purposes. Once we get the code in a more unified
state, then we can add more to the "DTP build." What this "more unified
state" is would be determined by the PMC in conjunction with the DTP
committers.

2. Actually doing the builds: For the time being, I think we should put
builds up manually as needs arise. For example, Der Ping and I have a talk
next week about DTP, and it would be nice to have a Model Base build
available. WTP wants to look at the connectivity frameworks, so I'd like to
have a "build" (maybe not fully functional) of that as soon as Rob gets the
initial code checked in. These builds could be done against a known base
set ("driver", such as Eclipse version, etc.) by individuals and then
posted on the site by me. Next, we'll move to automated builds/posting as
we get more components together. Ultimately, we'd have unit tests run, and
nice pictures (like the platform does) to show build status. Sybase has
agreed to host the build machine itself. I'd like to suggest that each
project be responsible for creating a build script that works within
certain parameters (not yet determined), and then I'll make sure that the
build machine automates running of those scripts. BTW, BIRT -- is there
some way we can generate interesting build reports for positing on the
site?

Thoughts?

Regards,
John Graham
Staff Software Engineer
Sybase, Inc.
telephone: (978) 287-1634  (GMT - 5)
e-mail: john.graham@xxxxxxxxxx



                                                                           
             "Linda Chan"                                                  
             <LChan@xxxxxxxxxx                                             
             m>                                                         To 
                                       "Der Ping Chou" <dpchou@xxxxxxxxxx> 
             08/25/2005 08:47                                           cc 
             PM                        <jograham@xxxxxxxxxx>, "Lawrence E  
                                       Dunnell" <ledunnel@xxxxxxxxxx>      
                                                                   Subject 
                                       RE: ODA plugin                      
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Hi Der Ping,

The compiler warning on assert seems to be related to the javac option
using a version older than 1.4 .
Did you use the Ant build script that comes with the ODA plugin source
tree?  It's called "build.xml" which references the "build.properties"
file.   It explicitly specifies version 1.4 for javac.
If so, perhaps there are other build environment options that should be set
as well.   Please feel free to give me a call, so we can walk thru them.

And yes, I fully agree that we need a build system in place for all the DTP
components.  In fact, John and I have discussed that briefly...   we need
volunteers to take this on   ;-)

Linda
office:  1-650-837-2217
      -----Original Message-----
      From: Der Ping Chou [mailto:dpchou@xxxxxxxxxx]
      Sent: Thursday, August 25, 2005 5:33 PM
      To: Linda Chan
      Cc: jograham@xxxxxxxxxx; Lawrence E Dunnell
      Subject: ODA plugin


      Linda,

      Since we don't have a build system in place for DTP yet. (I think it
      is something that we need to include in our milestone 1) While
      preparing course material for DTP in EclipseWorld, I was not able to
      build some helper classes (for example, odaDriver.java file - assert
      method is not defined) in org.eclipse.datatools.connectivity.oda
      plugin. Could you let me know what is the required build environment
      for oda?

      Thanks,

      Der-Ping Chou
      Information Management Tooling
      Development Manager - Data Tools
      Seattle IBM Office
      tel : 1-206-587-5946 (T/L: 277-5946)