uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (Commented) (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-2360) uima-as build broken due to missing uimaj 2.4.0 artifacts in maven central
Date Wed, 08 Feb 2012 13:55:59 GMT

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

Marshall Schor commented on UIMA-2360:
--------------------------------------

I found a method to re-upload the 2.4.0 release to the staging repository.  The method (for
those who are curious): 1) check out the 2.4.0 tag.  2) do a mvn release:perform with an extra
parameter described in the release plugin documentation: -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/....
referencing the tagged version you want to stage.  

I did that and then discovered the 2.4.0 build for uimaj *on purpose* doesn't deploy the multi-megabyte
artifacts it builds.  The top uima parent pom has this bit in it:


          <!-- https://issues.apache.org/jira/browse/UIMA-2008 -->
          <!-- no maven deployment of this project's artifacts -->
          <!-- binary build artifact deployed from apache mirror system after release -->
          <plugin>
            <artifactId>maven-deploy-plugin</artifactId>      
            <configuration>
              <skip>true</skip>   <!--  **** Causes deployment uploading to
be skipped **** -->
            </configuration>
          </plugin>

Keeping large assemblies that are distributed by the Apache "mirror" system (that are not
otherwise needed by Maven users) out of Maven central seems right to me.  So, I think we leave
the uima sdk build as it is, and instead should change the uima-as build.  It needs the uima
sdk binary assembly to build upon; that is available on www.a.o/dist/uima (but only while
current) and archive.a.o/dist/uima (always).  For efficiency, the download of this assembly
should be cached - probably the best place is the .m2 repository. I'll look into how to do
this.
                
> uima-as build broken due to missing uimaj 2.4.0 artifacts in maven central
> --------------------------------------------------------------------------
>
>                 Key: UIMA-2360
>                 URL: https://issues.apache.org/jira/browse/UIMA-2360
>             Project: UIMA
>          Issue Type: Bug
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>
> The UIMA SDK release generates an assembly binary distribution zip file.  The release
should have pushed this to maven central - allowing the uima-as build to download this artifact
and unzip it, to enable binary uima-as builds to include base UIMA.
> However, the last UIMA release failed to upload these to Maven Central.  Ask on infrastructure
for help in uploading these missing artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message