Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
TigerstripeF2F 20080616
Revision as of 21:15, 16 June 2008 by Erdillon.cisco.com (Talk | contribs) (→Packages as Artifacts)
Contents
< To: Tigerstripe Face2Face Meetings
0.3 Release
- Finalizing for tag v200806161700
- Documentation to be updated in Wiki
- Release Review scheduled for June 26th, 2008
- Asked for IPLog review
Metamodel Changes
Packages as Artifacts
Adding packages as artifacts of the metamodel means:
- Addressing Persistence
- persisted as ".package" in each package directory
- contains a dummy Class without body, we're only interested in the comment so we can re-use parsing/persistence velocity templates in place
- will be hidden from Tigerstripe Explorer
- IPackageArtifact as an extension of IAbstractArtifact
- no additional stuff, but turn off Abstract and others possibly through inheritence
- Add to IModelComponent
Collection<IModelComponent> getContainedComponents() IModelComponent getContainingComponent()
- Editor
- No major issue
- Maybe a bit of refactoring (extends, e.g.)
- Appearance
- in Explorer
- .package is not visible
- right-click to open in editor
- enhance content provider to show dependencies ends (as well as association ends for other artifacts)
- in Class Diagrams
- Show package on diagram
- Allow to "draw" dependencies
- Dependency Diagrams
- in Explorer
- Auditor
- no specific auditing rule
- Appropriate extension points to checked to allow for validation of explicit dependencies against implicit dependencies.
Note: package dependencies are captured directly through DependencyArtifacts as they currently exist.