loom

Convert to MetaClass for Generic MetaData access

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta1
  • Fix Version/s: 1.0-beta1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

When MetaClass matures, stabilizes and has good coverage for all it's unit tests we should migrate to it for our native metadata format. Internally we can use MetaClass to represent the information but it can be loaded from multiple sources - even aggregated from several sources. ie MXInfo + BlockInfo can be aggregated into a single MetaClass instance for legacy support.

Issue Links

depends upon

New Feature - A new feature of the product, which has yet to be developed. META-22 Document MetaClass-JMX tags

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Peter Donald added a comment -

The Loom upgrade to MetaClass depends upon SPICE-38 being completed.

Show
Peter Donald added a comment - The Loom upgrade to MetaClass depends upon SPICE-38 being completed.
Hide
Permalink
Peter Donald added a comment -

Initial task has been completed. BlockInfo and MXInfo are no longer used in Loom. The change is backwards incompatible and developers should regenerate metadata for their classes by running ant task over source code again.

Show
Peter Donald added a comment - Initial task has been completed. BlockInfo and MXInfo are no longer used in Loom. The change is backwards incompatible and developers should regenerate metadata for their classes by running ant task over source code again.

People

  • Assignee:
    Peter Donald
    Reporter:
    Mauro Talevi
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: