Bug 1032258

Summary:	Ivy doesn't include a POM file
Product:	[Fedora] Fedora	Reporter:	Will Benton <willb>
Component:	apache-ivy	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	mizdebsk, mspaulding06, msrb, orion
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.3.0-4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-04 09:36:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Will Benton 2013-11-19 20:13:54 UTC

Description of problem:

Per the Java packaging guidelines, Java packages should include POM files.  Ivy does not.  This makes it difficult to package other software that depends on Ivy.

Version-Release number of selected component (if applicable):

apache-ivy-2.3.0-1

Steps to Reproduce:
1. rpm -ql apache-ivy | grep pom

Actual results:

Fails.

Expected results:

Shows the path of a valid POM file.

Comment 1 Mikolaj Izdebski 2013-12-04 09:27:06 UTC

Fixed in apache-ivy-2.3.0-4

Comment 2 Mikolaj Izdebski 2013-12-04 09:36:17 UTC

I believe that this bug is fixed in apache-ivy-2.3.0-4,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=482611

This bug was fixed in the next release of Fedora, and is not planned
to be fixed in the release it was filed against.  If you want this bug
to be fixed in updates for Fedora 19, please say so in a comment.
Otherwise you can update to the newer release of Fedora to get the fix.