Thanks for your quick testing / checking. Some answers below. On 7/20/2013 3:35 PM, Richard Eckart de Castilho wrote: > Cleared local repo fully. > > Checked out tag and built: ok. > > Installed Eclipse plugins in dropins folder and checked if usual editors etc. > are present: ok. > > Opened description in Component description editor: ok. > > Upgraded uimaFIT to uimaj 2.4.1 artifacts and built: ok. > >> [X] +1 OK to release > > Some remarks though: > > uimaj-2.4.1-bin.zip - README - Document title not properly aligned with > horizontal line below
hmmm, looking at this in an plain text editor (monospaced fonts), everything seems to line up. Can you say more about what's wrong? > > > uimaj-2.4.1-bin.zip - resource should never be outside packages / at root of > JAR: > uima-core.jar - "resourceSpecifierSchema.xsd" and "uima.ecore" > uima-tools.jar - JCasGenFileConsoleLogger.properties Why do you assert this; can you say more? These have been at those locations since the early days. I suspect that user code would (by now) have dependencies on this positioning, and moving these would be disruptive. The normal reason to put things into packages is to avoid name conflicts where that's somewhat likely (due to (usually) hundreds of names being generated by different developers over time). The down-side is that the "names" get longer (as they are prefixed by package names). > > > uimaj-2.4.1-bin.zip - library names in lib folder inconsistent: > uima-core.jar > uima-cpe-jar > … > but: uimaj-bootstrap.jar > Shouldn't these all be uimaj-*? I agree they're inconsistent. The names are the way they are for I think purely historical reasons. There was debate (much) earlier on the mailing lists about names, mainly around following more normal Maven naming conventions, where the name of the Jar includes the version information. It was thought (back then) that changing the names would annoy users who were upgrading, and who would (potentially) need to change scripts when installing a new version. So, we've left these alone to enhance user stability. The "j" suffix on uima arose when it was realized that there were a variety of uima implementations for different language embeddings - j for java, cpp for C++, being the main 2. Projects that apply to all of uima, such as the big docbooks, have uima- prefixes :-). > > > uimaj-2.4.1-bin.zip - Why are the docs not in the "docs" folder, but in > "docs/d"? This was done along time ago as part of the docbook design which, if the docs are in a particular folder structure, can be used to generate proper cross-docbook links in PDF documents as well as html docs, both on the website, and when people download these to local disk. This was also intended to faclitate sharing and standardization of common boilerplate. See: http://uima.apache.org/dev-docbook.html ; the /d/ directory was intended to be the shared "docbook bookshelf" that made this possible. Finally, at one point, we had an arrangement with "infra" where we could avoid putting into SVN large generated documentation (think of the big sets of javadocs, as well as our html / pdf "books"), and yet have these available on our website. This arrangement was an rsync from people.a.o in our website docs/d directory, to the real website in the same directory. This arrangement was teminated by infra when they decided to have everyone use SVN pubsub or their CMS system for websites. -Marshall > > -- Richard > > > Am 20.07.2013 um 00:30 schrieb Marshall Schor <[email protected]>: > >> Hi, >> >> I've posted rc-3. The source and binary zips/tars are staged to >> http://people.apache.org/~schor/uima-release-candidates/2.4.1SDK-rc3/ >> <http://people.apache.org/%7Eschor/uima-release-candidates/2.4.1SDK-rc3/> >> >> The eclipse-update-site is >> http://people.apache.org/~schor/uima-release-candidates/2.4.1SDK-rc3/eclipse-update-site/uimaj/ >> <http://people.apache.org/%7Eschor/uima-release-candidates/2.4.1SDK-rc3/eclipse-update-site/uimaj/> >> >> The Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapacheuima-160/org/apache/uima/ >> >> The SVN tags are: >> https://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.4.1-rc3/ and >> for the eclipse udpate site: >> https://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.4.1-rc3/ >> >> The issues resolved/closed: 81 issues >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.4.1SDK%22%20AND%20status%20in%20(Resolved%2C%20Closed) >> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.4.1SDK%22%20AND%20status%20in%20%28Resolved%2C%20Closed%29> >> >> See http://uima.apache.org/testing-builds.html for suggestions on how to test >> release candidates. >> >> Please vote on release: >> >> [ ] +1 OK to release >> [ ] 0 Don't care >> [ ] -1 Not OK to release, because ... >> >> Thanks. >> >> -Marshall >
