Twitter github

Project Set Files (PSF)

I was recently working with the Apache Commons Httpclient library to move it into the Orbit project. Mylar (and other projects) was looking forward to using this library out of Orbit directly instead of including it as an additional library (yuck!). Eugene Kuleshov recently commented about how painful it would be for developers to work with Orbit bundles because developers would have to grab bundles from another repositories in order to get their workspace compiling. Well, let me introduce you to something called Project Set Files. They are a form of black magic that comes from the Team “team.” PSFs allow you to quickly materialize a workspace and are commonly found in “releng” projects (for Eclipse projects that know about them). I highly recommend using them πŸ™‚

  • Wayne

    They are very nice.

  • Wayne

    They are very nice.

  • Eugene Kuleshov

    I don’t like the black magic, but I do like your optimism Chris. Gon’t get me wrong, I am well aware of the project sets, but unfortunately many others had no clue about this quite old feature. Even Wayne… πŸ™‚

    Also, you should have noticed from my comments that Mylar is rather pessimistic about whole Orbit thing, because it don’t really buys that much to the project, but we have to deal with all kind of issues for the price of using Orbit. Maybe you can try to sell me into it in your next blog post. πŸ˜‰

  • Eugene Kuleshov

    I don’t like the black magic, but I do like your optimism Chris. Gon’t get me wrong, I am well aware of the project sets, but unfortunately many others had no clue about this quite old feature. Even Wayne… :-)Also, you should have noticed from my comments that Mylar is rather pessimistic about whole Orbit thing, because it don’t really buys that much to the project, but we have to deal with all kind of issues for the price of using Orbit. Maybe you can try to sell me into it in your next blog post. πŸ˜‰

  • Mik Kersten

    Just to clarify: Mylar is not inherently negative to using Orbit, and we have been pushing for common consumption of dependencies early on and were happy to see the Orbit effort.

    One of the key things that has stopped us moving so far is not wanting to raise the complexity to having developers contribute to Mylar and having integrators extend Mylar by using it from CVS (this encourages the contribution of patches). We also have some technical issues (e.g. some connectors currently require a specific Axis version to be in the same class loader as their plug-ins), and we still have to make sure the move does not overly complicate our build process.

    Project sets really are a great mechanism and we have been encouraging their use for a long time. Since there are developers who are not aware of them, we have so far also made it possible to check out the entire top-level Mylar directory and have things build without error. But as indicated on the bug below we will be evaluating the move to Orbit again for Mylar 2.0M3, and we have been advertising project sets as the main mechanism for getting the sources. The neat thing with project sets is that we can include the Orbit projects in the Mylar project sets.

    Further discussion on Mylar-specific concerns related to this would be best on the following bugs, so that it is easy to recall should we need to revisit it.

    167362: move httpclient dependency to Orbit

    172264: move Axis dependency into Orbit

  • Mik Kersten

    Just to clarify: Mylar is not inherently negative to using Orbit, and we have been pushing for common consumption of dependencies early on and were happy to see the Orbit effort.One of the key things that has stopped us moving so far is not wanting to raise the complexity to having developers contribute to Mylar and having integrators extend Mylar by using it from CVS (this encourages the contribution of patches). We also have some technical issues (e.g. some connectors currently require a specific Axis version to be in the same class loader as their plug-ins), and we still have to make sure the move does not overly complicate our build process.Project sets really are a great mechanism and we have been encouraging their use for a long time. Since there are developers who are not aware of them, we have so far also made it possible to check out the entire top-level Mylar directory and have things build without error. But as indicated on the bug below we will be evaluating the move to Orbit again for Mylar 2.0M3, and we have been advertising project sets as the main mechanism for getting the sources. The neat thing with project sets is that we can include the Orbit projects in the Mylar project sets.Further discussion on Mylar-specific concerns related to this would be best on the following bugs, so that it is easy to recall should we need to revisit it. 167362: move httpclient dependency to Orbit172264: move Axis dependency into Orbit

  • Eugene Kuleshov

    I guess my choice of word “pessimistic” was rather bad. I meant to say that last evaluation of moving dependencies to Orbit didn’t show real benefits to developers and integrators.

  • Eugene Kuleshov

    I guess my choice of word “pessimistic” was rather bad. I meant to say that last evaluation of moving dependencies to Orbit didn’t show real benefits to developers and integrators.