I've updated the KEYS under /www/www.apache.org/dist/uima/KEYS it should be
online in a short time.

2011/4/28 Marshall Schor <[email protected]>

> I unzipped the binary build.
>
> It has a "lib-osgi" and a "lib".  These both have jars.
>
> The lib-osgi is 59.8 MB, while the lib is 6.2 MB.  Is this to be expected?
> (How
> come the lib-osgi jars are ~ 10 x bigger?).
>

this is expected as the components' bundles contain the dependencies
"bundled" inside the jar in order to allow easy deploy in OSGi containers
(i.e. Apache Felix).


>
> I note also that the names of the lib-osgi jars have "SNAPSHOT" in them -
> something didn't do the right thing with these to remove this.
>

the -SNAPSHOT shouldn't have been there, I'll release:rollback and fix that.

One more thing I noticed is the $annotator-osgi don't have LICENSE/NOTICE
while I think they're needed.

2011/4/28 Marshall Schor <[email protected]>

> The Jira report is using the wrong sort order.
>
> This was fixed in the next release of the UIMA - wide parent pom, but until
> that
> is released, you have to fix it by overriding in the parent pom for the
> addons
> project.
>
> See: https://issues.apache.org/jira/browse/UIMA-2071


Right, I'll fix that.
Thank you very much Marshall.
Tommaso




>
> -Marshall
>
> On 4/26/2011 10:47 AM, Tommaso Teofili wrote:
> > Hi all,
> > the first UIMA Addons 2.3.1 release candidate is ready for testing, you
> can
> > checkout the SVN tag [1] to build it from sources or get the created
> > artifacts (source and binary) at [2].
> > Note that this is release will include the whole set of maintained
> > components in the sandbox while in the future we may want to release
> sandbox
> > artifacts independently.
> > I've issued only the release:prepare command so that small issues can be
> > rollbacked easily.
> > Any feedback is welcome before we call for a vote.
> > Regards,
> > Tommaso
> >
> > [1] :
> > http://svn.apache.org/repos/asf/uima/sandbox/tags/uima-addons-2.3.1-rc1/
> > [2] : http://people.apache.org/~tommaso/uima-addons-2.3.1-rc1/
> >
>

Reply via email to