Re: [stem-dev] Features and Feature project naming

[James Kaufman <kaufman@xxxxxxxxxxxxxxx>]

Hi Dan,
Matt is already working on implementing
features. The first target is to organize some of the earth science data
a separate features
as we want to add ten years of data
and for each year the plugin is quite large.

We want to keep STEM easy to install
for the public health community and as an epidemiological modeler it makes
sense to 
continue to keep basic disease and population
models as core. 

It would be great if you could join
the call today to discuss. I'm sure Matt would welcome your input.

 Best Regards,
Jamie

IBM Almaden Research Center, 650 Harry Rd.
San Jose, CA 95120-6099
email: kaufman@xxxxxxxxxxxxxxx
phone: (408) 927-2477  (tie 457-2477)

From:	Daniel Ford <webdaford@xxxxxxxxxxxxxxxx>
To:	stem-dev@xxxxxxxxxxx
Date:	04/28/2011 08:19 AM
Subject:	[stem-dev] Features and Feature project naming
Sent by:	stem-dev-bounces@xxxxxxxxxxx

---

I was working on the project today and took at look
at the features.  I 
noticed that three had unconventional naming.  They were:

org.eclipse.stem.feature.core
org.eclipse.stem.feature.internal.data
org.eclipse.stem.feature.prereq

Typically, for Eclipse projects, the names of Feature projects would 
have "feature" as a suffix.  E.g.

org.eclipse.stem.core.feature
org.eclipse.stem.internal.data.feature
org.eclipse.stem.prereq.feature

I have long advocated that we organize the project around "Features,"
and I think that this would be a good time to start doing that.  In
the 
process I think we should adopt the conventional naming structure used
by other Eclipse projects for their Features.  STEM currently has
ninety-six Eclipse plug-ins in SVN, but only five features; two of those
don't seem to be used currently.

I'm going to start defining more features and would like input on that
process.

Dan



_______________________________________________
stem-dev mailing list
stem-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stem-dev