Hello Michiel, The Eclipse projects can have rules about what packages are accessible by other Eclipse projects. This way, access to internal packages can be discouraged and only the public packages could be exported.
You can mark which packages should be exported to be used by other Eclipse projects (eg ArgoEclipse) by opening the META-INF/MANIFEST.MF for the argouml Eclipse project then go to Runtime tab and in the "Exported Packages" section you should see all the argouml exported packages. You can use the "Add..." button to add more packages that should be exported (eg org.argouml.taskmgmt). Bogdan On 4/29/07, Michiel van der Wulp <[EMAIL PROTECTED]> wrote:
Hi All, Today, I tried to add the ArgoEclipse project to my development environment, so that I can adapt this project, too, when I change something in ArgoUML. So, I got the only ".psf" file for Eclipse, and added only the projects I did not have yet: 8 projects named argoeclipse-*. Now, I added a new package in ArgoUML, only to find out, that access to it is restricted by some unmodifiable rules. E.g. all projects that use argouml have in their properties JavaBuildPath -> Libraries -> Plug-in Dependencies -> argouml -> Access rules: 75 rules defined, added to all project child entries - non modifiable. This list of 75 packages needs to be extended with a 76th item, i.e. the package that I just created. How can I do that? Why do we have these rules? How do I get rid of them? Regards, Michiel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
