Hi Richard, before we do something here, I'm wondering if you've considered a delegation model, rather than subclassing.
Subclassing tends to create a rather tight coupling between a class and its subclass, in terms of maintenance and changes, while delegation doesn't; several articles I've seen seem to favor delegation over inheritance. Would a delegation model work in this case for what you want to experiment with? -Marshall On 8/18/2011 2:29 AM, Richard Eckart de Castilho wrote: > Hi, > > would you mind addressing https://issues.apache.org/jira/browse/UIMA-2102 > before the 2.3.2 release? > > Cheers, > > Richard > > Am 17.08.2011 um 17:37 schrieb Marshall Schor: > >> ok, I'll do this restructuring, under >> https://issues.apache.org/jira/browse/UIMA-1967 >> >> -Marshall >> >> On 8/17/2011 10:21 AM, Jörn Kottmann wrote: >>> On 8/17/11 4:10 PM, Marshall Schor wrote: >>>> I'd like to do a release of the base UIMA SDK soon. >>>> >>>> We've tried the alternative structure, of putting a top-level pom in the >>>> directory above the projects, for the addons. This structure is more >>>> conventional for Maven projects, but creates a bit of "noise" in the >>>> Eclipse IDE >>>> (the projects appear twice). >>>> >>>> I'm personally comfortable with moving to the more conventional structure; >>>> would >>>> others object if I convert the base UIMAJ project structure to that style? >>>> >>> I am also +1, because it makes things easier. >>> >>> Jörn >>> > Richard Eckart de Castilho >
