This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 137239 - Adding a standard <<manifest>> dependency
Summary: Adding a standard <<manifest>> dependency
Status: RESOLVED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Deployment (show other bugs)
Version: 6.x
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@uml
URL: http://catslair.org/files/syncDeploy.jpg
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-14 23:30 UTC by liono
Modified: 2009-07-30 21:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description liono 2008-06-14 23:30:56 UTC 
My main source of information here is the O'Reilly UML 2.0 book. Its common for an artifact to display a manifestation
by adding a relationship between the manifest and a component. For example, in the diagram in the URL the manifestation
shows that the jarfile is providing either the server or client component (actually its providing both but thats a whole
different discussion).

So I think it would be a welcome addition if there were a standard way to setup a <<manifest>> association.
Comment 1 liono 2009-07-30 21:14:39 UTC 
I'm moving this to fixed because the plugin project has evolved since then and as far as I can see this behavior is
supported now.