[jira] Updated: (QPID-1916) Maven releases for the client and management jars

["Emmanuel Bourg (JIRA)" <qp...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated QPID-1916:
---------------------------------

    Attachment: maven.patch

I attached an alternative patch to generate the Maven artifacts:

- like Bryan's patch it's based on the Maven Ant tasks, it installs the artifacts in the local repository and copy them in the release directory of the module.

- the name of the artifacts has been changed from <module> to qpid-<module>. That's necessary to get the name of the jar right in the repository (qpid-client-<version>.jar instead of client-<version>.jar)

- a source bundle is generated, when imported into an IDE it provides a convenient contextual help (quick javadoc lookup, parameters names)

- the release.sh script has been modified to pickup the maven artifacts and sign them automatically. After uploading the files to people.apache.org the following document explains how to deploy them into the Apache repository : http://commons.apache.org/releases/release.html#a3_Deploy_Maven_Artifacts

Snapshot artifacts based on this patch are available here:

    http://people.apache.org/~ebourg/qpid/maven/



> Maven releases for the client and management jars
> -------------------------------------------------
>
>                 Key: QPID-1916
>                 URL: https://issues.apache.org/jira/browse/QPID-1916
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Ant Build System, Build Tools, Java Client, Java Common, Java Tools, Maven build system, Qpid Managment Framework
>            Reporter: Bryan Kearney
>         Attachments: maven.patch, mavenize3.patch
>
>
> The attached patch files adds the maven ant tasks to the build system. It allows, on a per-module basis, to support creating a pom file and exporting the jars to a maven repository. This is not a very DRY solution, as it requires copying the dependency information from the build.deps file. I have only added the pom files for the client bits, since i believe these are the most likely to be required by folks using QMF.

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org