[jira] [Commented] (RIVER-317) Deploy Apache River artifacts to Maven repositories (both release and snapshot)

["Jonathan Costers (JIRA)" <ji...@apache.org>]

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

Jonathan Costers commented on RIVER-317:
----------------------------------------

The "deploy-artifacts" task, which is already present in build.xml, should allow us to integrate this into our CI builds, if we set the right location in property m2.repository:

<!-- TODO: cleanup and find out where exactly to publish to -->
   <!-- Note that you need the Maven Ant tasks (http://maven.apache.org/ant-tasks/)
       installed to use this task -->
   <target name="deploy-artifacts" depends="jars">
       <!--<artifact:install-provider artifactId="wagon-file" version="1.0-beta-2"/>
       <artifact:install-provider artifactId="wagon-http" version="1.0-beta-2"/>
       <artifact:install-provider artifactId="wagon-ssh" version="1.0-beta-2"/>-->
       <!-- Override this in <river src distr. home>/build.properties to try out -->
       <property name="m2.repository" value="file:///home/jonathan/maven" />
       <macrodef name="deploy">
           <attribute name="file" />
           <attribute name="pom" />
           <sequential>
               <artifact:deploy file="@{file}" >
                   <remoteRepository url="${m2.repository}"/>
                   <pom refid="@{pom}"/>
               </artifact:deploy>
           </sequential>
       </macrodef>
       <artifact:pom id="parent" file="${poms.dir}/pom.xml" />
       <artifact:pom id="jini-core" file="${poms.dir}/jini-core/pom.xml" />
       <artifact:pom id="jini-ext" file="${poms.dir}/jini-ext/pom.xml" />
       <artifact:pom id="jsk-lib" file="${poms.dir}/jsk-lib/pom.xml" />
       <artifact:pom id="jsk-dl" file="${poms.dir}/jsk-dl/pom.xml" />
       <artifact:pom id="jsk-resources" file="${poms.dir}/jsk-resources/pom.xml" />
       <artifact:pom id="jsk-platform" file="${poms.dir}/jsk-platform/pom.xml" />
       <artifact:pom id="jsk-policy" file="${poms.dir}/jsk-policy/pom.xml" />
       <artifact:pom id="serviceui" file="${poms.dir}/serviceui/pom.xml" />
       <artifact:pom id="sun-util" file="${poms.dir}/sun-util/pom.xml" />
       <artifact:pom id="start" file="${poms.dir}/start/pom.xml" />
       <artifact:pom id="tools" file="${poms.dir}/tools/pom.xml" />
       <deploy file="${lib.dir}/jini-core.jar" pom="jini-core" />
       <deploy file="${lib.dir}/jini-ext.jar" pom="jini-ext" />
       <deploy file="${lib.dir}/jsk-lib.jar" pom="jsk-lib" />
       <deploy file="${lib-dl.dir}/jsk-dl.jar" pom="jsk-dl" />
       <deploy file="${lib.dir}/jsk-resources.jar" pom="jsk-resources" />
       <deploy file="${lib.dir}/jsk-platform.jar" pom="jsk-platform" />
       <deploy file="${lib-ext.dir}/jsk-policy.jar" pom="jsk-policy" />
       <deploy file="${lib.dir}/serviceui.jar" pom="serviceui" />
       <deploy file="${lib.dir}/sun-util.jar" pom="sun-util" />
       <deploy file="${lib.dir}/start.jar" pom="start" />
       <deploy file="${lib.dir}/tools.jar" pom="tools" />
   </target>

> Deploy Apache River artifacts to Maven repositories (both release and snapshot)
> -------------------------------------------------------------------------------
>
>                 Key: RIVER-317
>                 URL: https://issues.apache.org/jira/browse/RIVER-317
>             Project: River
>          Issue Type: Task
>          Components: Web site and infrastructure
>    Affects Versions: River_2.1.2, River_2.2.0
>            Reporter: Jeff Ramsdale
>             Fix For: River_2.2.1
>
>         Attachments: river-poms.patch
>
>
> It would be valuable if Apache River artifacts were deployed to a Maven repository upon release. It would be even better if snapshot builds were also deployed to a snapshot repository by Hudson.
> See thread: http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200908.mbox/<e2...@mail.gmail.com>



--
This message was sent by Atlassian JIRA
(v6.1#6144)