[JBOSGI-778] Centralize module OsgiMetaData reading logic - Red Hat Issue Tracker

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Details

Type: Enhancement
Status: Resolved
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: JBossOSGI 2.3.1
Component/s: framework, resolver, wildfly
Labels:
None

Git Pull Request:
https://github.com/jbosgi/jbosgi-resolver/pull/9, https://github.com/jbosgi/jbosgi-framework/pull/24, https://github.com/jbosgi/jbosgi-repository/pull/15, https://github.com/jbosgi/jbosgi/pull/11

Description

Module OSGiMetaData processing is all over the place and needs to be centralized
OSGiMetaData attachment to XBundleRevision needs to be reviewed

Attachments

Issue Links

follows up on

JBOSGI-777 Filter-out zero-length path from module-exported paths

Resolved

JBOSGI-774 Cleanup solution for JBOSGI-567

Resolved

JBOSGI-775 ServiceLoader should work with module dependencies and capabilities

Resolved

Activity

People

Assignee:: Arcadiy Ivanov (Inactive)

Reporter:: Arcadiy Ivanov (Inactive)

Archiver:: Sagar Mahajan

Dates

Created:: 2015/Apr/19 4:38 AM

Updated:: 2015/Jul/14 9:09 PM

Resolved:: 2015/Jul/14 9:09 PM

Archived:: 2021/Apr/17 5:14 AM