Bug 742212 - POMs & depmaps are missing in the bea-stax / bea-stax-api package
Summary: POMs & depmaps are missing in the bea-stax / bea-stax-api package
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bea-stax
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-29 12:13 UTC by Jaromír Cápík
Modified: 2016-02-01 01:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-29 15:32:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jaromír Cápík 2011-09-29 12:13:56 UTC
Description of problem:
Hello.
Several new package updates are affected by missing POM filees & add_maven_depmap macros in the bea-stax package. That leads to need of depmap files in the new builds. Since it's more systematic to fix it here, please, rebuild the package with included POM files and corresponding add_maven_depmap macros.
We need the following groupId:artifactId pairs

stax:stax
stax:stax-api
javax.xml.stream:stax-api

... where the last one needs to be supplied with %add_maven_depmap -a "javax.xml.stream:stax-api" as a different groupID variant of "stax:stax-api"

stax-1.2.0 POM can be downloaded here:
http://dist.codehaus.org/stax/jars/stax-1.2.0.pom

stax-api-1.2.0 POM is not available ... please, ask upstream to provide us with one or alter the following one http://ftp.cica.es/mirrors/maven2/stax/stax-api/1.0.1/stax-api-1.0.1.pom 

It would be also nice to update from 1.2.0rc1 to 1.2.0.

Thanks in advance.
BR, Jaromir.

Comment 1 Fedora Admin XMLRPC Client 2011-09-29 12:24:56 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Jaromír Cápík 2011-09-29 15:32:01 UTC
Rebuilt as 1.2.0 with depmaps and POMs... closing.


Note You need to log in before you can comment on or make changes to this bug.