Twitter github

We do tooling but our business is people

The Eclipse 3.3 release cycle has gone really well for the PDE team. Considering the relatively small size of the team, we’ve managed to fix a ton of bugs and add a plethora of new enhancements (from people who didn’t submit patches btw ;p). The PDE motto has always been, “We do tooling but our business is people.” With that stated, the PDE team is entering the polish phase of the release cycle and we implemented things known as “theme weeks.”

This week’s theme is “anything product related” needs to be polished. Next week is primarily all things cheat-sheets. We are inviting the community to comment and file new bugs that they would like solved before 3.3 closes. We will pay special attention to these requests and try to fit them in the plan as we understand that PDE plays an important in the future growth of Eclipse.

  • Villane

    If PDE wants to be a tool that supports building OSGi bundles really well, it should fix bug #157375: PDE should support building against nested JARs ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375 )

  • Villane

    If PDE wants to be a tool that supports building OSGi bundles really well, it should fix bug #157375: PDE should support building against nested JARs ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375 )

  • Chris Aniszczyk (zx)

    It would really be cool if your nested jars were just bundles. Everyone’s doing it!

  • Chris Aniszczyk (zx)

    It would really be cool if your nested jars were just bundles. Everyone’s doing it!

  • Wassim Melhem

    can you find me one compiler on Earth that can compile against nested JARs?

  • Wassim Melhem

    can you find me one compiler on Earth that can compile against nested JARs?

  • Eugene Kuleshov

    Wassim, the JDT compiler can consume artifacts from pretty much anything. You just need to give it appropriate provider implementation.

  • Eugene Kuleshov

    Wassim, the JDT compiler can consume artifacts from pretty much anything. You just need to give it appropriate provider implementation.

  • Jerome Lanneluc

    Eugene, I confirm that the JDT compiler cannot currently compile against nested JARs. There is no API to tell the compiler that a folder inside a JAR should be considered. And, as Wassim said, no other compiler can do this either. That might be an interesting feature to add in the future though.

  • Jerome Lanneluc

    Eugene, I confirm that the JDT compiler cannot currently compile against nested JARs. There is no API to tell the compiler that a folder inside a JAR should be considered. And, as Wassim said, no other compiler can do this either. That might be an interesting feature to add in the future though.

  • Philippe Mulet

    There is no *official* API. Maybe Eugene looked at the internal NameEnvironment API which indeed could be implemented to match this request (but not available as of today).

  • Philippe Mulet

    There is no *official* API. Maybe Eugene looked at the internal NameEnvironment API which indeed could be implemented to match this request (but not available as of today).