| RE: [mylar-dev] Internal Code |
|
When the cost of using those APIs (more to change between milestone releases, some functionality could stop working) exceeds the benefit feel free to use them. The Mylar Java component makes heavy use of internal APIs, and the new folding APIs that are in M3 probably wouldn't be there if we hadn't had a prototype implementation based on internal APIs to discuss. So communicating with the GEF team about your usage and needs is a great idea.
But what you should do is: (4) None of the above. Instead, go to your project properties, and add the following access rule: **/internal/** (Accessible). Then check in the corresponding change to the project’s .settings file so that others don’t see any warnings.
Thanks for bringing this up--I'll update the dev page.
Mik
> -----Original Message----- > From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx] > On Behalf Of Ian Bull > Sent: November 6, 2005 5:04 PM > To: Mylar developer discussions > Subject: [mylar-dev] Internal Code > > Is there a policy on the use of internal code in Mylar Components? I am > currently investigating the Time-Line view (Bug #109457 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=109457>), and during our > initial development, we are making use of internal GEF code. There are > several GEF Ruler classes that need to be extended, however, these > classes are all marked internal. I will work with the GEF team to get > these classes out of the internal packages, and into the stable API, but > this may take time. In the meantime we have several warnings because of > this. I currently see three solutions. > > 1) Leave the warnings > 2) Disable "internal code warnings" > 3) Copy the GEF code we need to our project. > > I have also thought about using the "suppress warnings" annotation, but > this doesn't seem to work for access rule warnings. (Plus we are trying > to keep this component available to Java1.4 users too). > > Cheers, > Ian > _______________________________________________ > mylar-dev mailing list > mylar-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/mylar-dev |
