Bug 917624

Summary: javamail: Please add Maven depmaps for org.eclipse.jetty.orbit artifacts
Product: [Fedora] Fedora Reporter: Mikolaj Izdebski <mizdebsk>
Component: javamailAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mizdebsk, msrb
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 1.4.3-16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-06 12:43:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 917618    
Attachments:
Description Flags
Proposed patch none

Description Mikolaj Izdebski 2013-03-04 12:20:35 UTC 
Description of problem:
Eclipse relocated various artifacts under their own groupId -
org.eclipse.jetty.orbit. Please additional depmaps to appropriate
artifacts in javamail package.

The following artifacts need to have depmaps added with groupId
org.eclipse.jetty.orbit:
  * javax.mail.glassfish

For more information on how to add extra mappings see Java packaging
guidelines[1], especially the part describing %add_maven_depmap macro[3].

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

Additional info:
[1] http://fedoraproject.org/wiki/Packaging:Java
[2] http://fedoraproject.org/wiki/Packaging:Guidelines
[3] http://fedoraproject.org/wiki/Packaging:Java#add_maven_depmap_macro
Comment 1 Mikolaj Izdebski 2013-03-04 12:30:12 UTC 
Created attachment 704939 [details]
Proposed patch
Comment 2 Mikolaj Izdebski 2013-03-06 12:25:22 UTC 
Fixed in javamail-1.4.3-16
Comment 3 Mikolaj Izdebski 2013-03-06 12:43:37 UTC 
I believe that this bug is fixed in javamail-1.4.3-16,
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=400285