| Re: [tycho-user] What is the latest on "Access restriction" compilation errors |
Tonny's suggestion is basically what I've done, but it sure feels "icky" and I don't like that it means any further usage of com.sun.* packages in that plugin will be masked/ignored. What I really don't get is why Eclipse (and PDE) don't warn about it? As I said, I definitely have the compiler settings configured to create warning markers for accessing restricted classes; it's frustrating that Tycho and Eclipse aren't in sync on this. Doesn't Eclipse normally flag such access with a warning? More below… On 11/28/12 1:29 AM, "Mickael Istria" wrote: Extensions Bundle are the only good way to go with clean OSGi. Actually, our software does in fact run against a specific JRE; we bundle the JRE with the product. I have asked the team responsible for the code to investigate removing the com.sun.* usage, but there is no guarantee that a reasonable alternative exists (I've yet to find another implementation of CachedRowSet other than vendor-specific ones). If an extension bundle is really what OSGi wants to push me to, why doesn't Eclipse PDE complain about the access? Where is it configured that the com.sun.rowset package (or any package, for that matter) is "restricted" in the JRE? How can we expect a team of 100+ developers to know what Tycho or OSGi is going to be sensitive to when the IDE doesn't provide guidance? Eric On 11/28/12 3:15 AM, "Tonny Madsen" wrote: If removing the dependency or adding an OSGi extension bundle is too difficult right now, you can also change the warning levels of the compiler with the following snippet: |