[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [higgins-dev] proposed dependency project
|
I'm forwarding this suggestion from Paul:
1. standardize on ONE way to describe dependencies: I suggest the .manifest file (yes, make every single higgins project a plugin project).
2. The local /lib folder should be used for non-reusable, not-of-general-interest .jars that are internal to the plugin and considered intrinsic to it. There should be very few of these.
2.1. Encourage folks not to put third party dependencies in /lib folders at all
3. Wrap every individual third-party jar in its own plugin project
I already put this on #higgins, and there was agreement at first, but then we all started talking about the Orbit project.
Orbit is probably the right way to go, and if it doesn't work for us, then it should be fixed. My problem is that I don't really know how it works.
Does Orbit do something like #3 above and provide a plugin project for every jar? The instructions at http://wiki.eclipse.org/Easy_Bake_Builds_with_Orbit_Bundles make it look like you're supposed to do something to your project's build which pulls down the jar file(s) you need.
Jim
