Bogdan explained the mechanics adding a new package to the Eclipse plugin manifest.
The reason this is needed is that the various ArgoUML Eclipse projects (argouml, argouml-core-lib, -core-model, -core-model-mdr) live dual lives as standalone projects and as Eclipse plugins. Eclipse has a rather clunky integration (or lack of integration) between the Build Path properties tab and the plugin manifest. It's not obvious how to navigate from one to the other if you don't know how upfront, even though they have a strong influence on each other. The access rules provide a way of defining and enforcing a public API to a particular plugin. By default Eclipse will automatically exclude any packages that have ".internal." in their name, but you can also explicitly include and exclude classes. In addition to the exports, you can also manage the classpath and compiler settings here. Eclipse will update the build properties from the manifest, but not vice versa, so it's best to update things on the manifest (although I can understand that this would be easy to forget if you're not doing plugin development, so the plugin developers need to take extra care to make sure they stay properly synchronized). Another way to navigate to the Eclipse plugin manifest is to use the context menu item from PDE Tools -> Open Manifest. Hope this additional background helps explain what's going on and why things are set up this way. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
