PDE can have compile time dependencies in its build.properties but naturally build.properties is not part of the final jar
Tom Von meinem iPhone gesendet > Am 09.05.2015 um 00:52 schrieb Stephan Herrmann <[email protected]>: > > I'm not responding to any of that religious anti-PDE flame war > which is totally inappropriate in this discussion. > > >> On 05/08/2015 10:21 AM, BJ Hargrave wrote: >> Well I suggest that (1) JDT not have a fatal error here since the goal is >> not to generate a class file > > Sounds like the obvious way to go, sure. > Just note that reporting this kind of error is not connected > to generating class files but to the semantic analysis, > which indeed is desired in this use case - which only means: > it's not as easy as just stopping before class file generation. > Continuing compilation on broken input is a main contributor > to complexity of this already very complex component. > That's why avoiding unnecessarily broken input sounds like > a much nicer option. > >> and (2) PDE should ... support a >> way to specify compile dependencies different than runtime dependencies > > Well, if that's what the OSGi spec says, it shouldn't be hard > to convince PDE ... > > Stephan > > _______________________________________________ > equinox-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
