On 11/20/2013 4:36 AM, Richard Eckart de Castilho wrote: > When you say "up", do you mean "up" in terms of svn directory structure, or > "up" in terms of quality (so to addons)? I meant, out of sandbox, to their own major level under uima. > > I don't get the difference between "top level" projects and addons projects. The addons are typically "smaller" than the other top level things, and were collected together into the "addons" folder to enable all them to be released as one thing.
> > Top-level is "mostly" framework, but also includes UIMA-AS. > > Addons is mostly components, but also contains stuff like the SimpleServer or > the PearPackagingAntTask. I'm not even sure as what to count the FsVariables. > > I don't see exactly how one can refer to all "current" level addons if they > have > different release cycles. Doing a binary ZIP release bundling all addons > whenever > any of them changes doesn't seem to be useful. We could set up an aggregator > POM > which depends on the individual modules in their respective latest versions. > But hum… I would personally prefer adding each required dependency > individually > instead of via an aggregator. What did you have in mind? I was thinking, from the viewpoint of a user, who might just want all the latest stuff. Consider how Eclipse does plugin packaging. When there's a new Eclipse release, you get a set of plugins. Not all of them are necessarily updated from release to release... Most of the plugins in the 4.3.1 release of Eclipse have v2013xxxx with varied months/days, but there are some going back to v2010xxxx. v2011xxxx, etc. So, not all of these are "re-released", but they're combined into an overall package that a user can get if they want. -Marshall
