[SDM-SPA] Re: [kepler-dev] moving edu.ncsu to org.sdm.spa

Bertram Ludaescher ludaesch at sdsc.edu
Wed Apr 7 08:30:41 PDT 2004

>>>>> "IA" == Ilkay Altintas <altintas at sdsc.edu> writes:
IA> Hi All,
IA> I understand we want the spa to be the top src folder in the 
IA> spa cvs and we have decided to have the util under it.
IA> But I believe it would be a better structure if we have it like
IA>    src
IA>     |_ org
IA>         |_ sdm
IA>            |_ spa
IA>                |_ util (SPA actor-specific utility files)
IA>     |_ util (Generic utility files)
IA> This will also make the synch with Kepler easier. We can copy 
IA> the generic util files we need from Kepler into the top directory.
IA> Copying all the geon folder just for using a geon util file 
IA> doesn't make very much sense to me. I thought this was what
IA> we wanted to avoid in spa cvs. Did I misunderstand something?
IA> Also for Kepler, it might be a better organization to keep 
IA> the project-related/actor-specific util files in project
IA> folders and the generic util files in one top directory under 
IA> source (***as it is now) IMHO. It is easier to look for what's 
IA> already available in the top folder, etc. and some of these 
IA> files would be even not belonging to a kepler project but 
IA> anonymous code that is being used by some of the actors. 
IA> (e.g. UUIDGen.java is a universal id generator is an open-source 
IA> (see author info in the file) java code that is used to create 
IA> unique temporary file names for temporary storage.)

I agree.

IA> There might be other ways of doing this. This is just an 
IA> idea that seemed reasonable to me. 
IA> Ilkay
IA> -----Original Message-----
IA> From: kepler-dev-admin at ecoinformatics.org
IA> [mailto:kepler-dev-admin at ecoinformatics.org]On Behalf Of Xiaowen Xin
IA> Sent: Tuesday, April 06, 2004 4:46 PM
IA> To: Ilkay Altintas; efrat at sdsc.edu
IA> Cc: sdm-dev at sdsc.edu; kepler-dev at ecoinformatics.org
IA> Subject: RE: [SDM-SPA] Re: [kepler-dev] moving edu.ncsu to org.sdm.spa
IA> Another thing is we agreed a few weeks ago that we would have a
IA> org/sdm/spa/util directory for utility files.  So what's currently in
IA> kepler/src/util would ideally go there.  This switch wouldn't be as easy
IA> to make since there's a GEON file that apparently uses both files that
IA> are currently in util/.
IA> Efrat: you're listed as the author for
IA> src/org/geon/OpenDBConnection.java, which is the only non-spa file I
IA> could find that uses the code in util/.  Would it be okay for me to move
IA> what's now in src/util into org/sdm/spa/util/?  Alternatively, we could
IA> move those two files into org/geon/util/.
IA> The reason for this is that since we're already dividing up most of the
IA> source files by organization, we should just divide it all up by
IA> organization.  I think the reason people wanted a util/ directory is so
IA> that it would be a place to put code that would be useful for all
IA> projects.  However, this criteria is hard to determine because most of
IA> the code from one project could potentially be useful in the other
IA> projects.  So I think having a util/ directory as a subdirectory of the
IA> projects makes more sense.  If SPA needed to use something from GEON, we
IA> could import org.geon.*; or org.geon.util.* as an example.  The
IA> distinction here between org.sdm.spa.* and org.sdm.spa.util.* is that
IA> util.* contains non-actor utility code, while all the actors go into
IA> org.sdm.spa.*.
IA> I hope that made sense :)
IA> Xiaowen
IA> _______________________________________________
IA> kepler-dev mailing list
IA> kepler-dev at ecoinformatics.org
IA> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
IA> _______________________________________________
IA> kepler-dev mailing list
IA> kepler-dev at ecoinformatics.org
IA> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev

More information about the Kepler-dev mailing list