You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Bryan Kearney (JIRA)" <qp...@incubator.apache.org> on 2009/06/18 17:42:07 UTC
[jira] Updated: (QPID-1916) Maven releases for the client and
management jars
[ https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Kearney updated QPID-1916:
--------------------------------
Attachment: mavenize.patch
Run the attached path file from the qpid directory. For the build to work, the maven ant tasks jar (version 2.0.10) must be downloaded from
http://maven.apache.org/download.html
and placed ino the qpid/java/libs directory
> 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: mavenize.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