On 1/30/2013 5:16 AM, Peter Klügl wrote: > On 29.01.2013 23:53, Marshall Schor wrote: >> Hi, >> >> I would suggest that you consider making the top level name of your project >> "textmarker" (without uimaj- in front). The uimaj prefix is strongly >> associated >> with the Java SDK for UIMA. >> >> (We have releases named uima-as (no "j") and uima-cpp, and many sandbox/addon >> projects with simple names that denote what they are.) > > No problem. The artifact id and projects should stay the same?
I think the artifact-id in the POM used when importing to generate the Eclipse Project name. So, the group name stays the same (org.apache.uima) of course, but the artifact name probably should follow some simple convention suggesting belonging-to-textmarker. SVN already has sandbox/TextMarker/trunk... in other words, there's no "uima-" in front of TextMarker. (I slightly prefer all lower case, but don't change this unless you want to: sandbox/textmarker/trunk.... ) Under that, I would go for something which had "textmarker-" in front trunk (id: textmarker) textmarker-docbook textmarker-ep-addons textmarker-ep .... other eclipse plugins textmarker-core textmarker-parent (if necessary) This gives a uniform easy way to keep all these things associated :-) and it's shorter than uimaj-textmarker. However, please consider this just a suggestion... I think it's basically your call. -Marshall > > > Here's a proposal to discuss: > > sandbox > - uima-textmarker > -- trunk (artifact id: uima-textmarker) > --- uima-docbook-textmarker > --- uimaj-ep-textmarker-addons > --- ... > --- uimaj-textmarker-core (was uimaj-textmarker with binary > "uima-textmarker.jar") > --- ... > --- uimaj-textmarker-parent (if necessary) > > > Best, > > Peter > >
