You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/04/23 16:01:23 UTC

[jira] Commented: (UIMA-1010) uima-as release process not capturing a known level of core uima

    [ https://issues.apache.org/jira/browse/UIMA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591648#action_12591648 ] 

Marshall Schor commented on UIMA-1010:
--------------------------------------

If the version of core uima that this uima-as release is based on is officially released, then this tagging is not needed, I think. For instance, consider the inclusion in uima-as of a particular version of the Spring framework.  We do not tag the source for the spring frame work; users wanting that can get it from the Spring website for that officially released version.

This need to tag things only occurs, I think, when the uima-as build is building upon a not-yet-officially-released version of core uima.  

Note that the assembly for uima-as binary specifies the version of uima being built upon, in the POM for the uima-as-distr project.


> uima-as release process not capturing a known level of core uima
> ----------------------------------------------------------------
>
>                 Key: UIMA-1010
>                 URL: https://issues.apache.org/jira/browse/UIMA-1010
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout, Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.2.2AS
>
>
> The current uima-as release process does not tag a level of the core uima used to supply its lib/jars; it uses whatever is in the builder's local  maven repository, which may be in some unknown state.  Attaching the right source to these jars is difficult, if not impossible (impossible if there were local uncommitted changes in the builder's system, that were used to build the local repo, but never checked in.)
> The release process needs to tag the version of core uima that uima-as is based on, and extract that and build it before building uima-as.
> The source distribution for uima-as should include a pointer to the tag in svn (the source distr for core uima is large mainly due to documentation, doc tooling, and tests).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.