Hi Austin, personally, I think including a project-set-file (.psf) in your bundle, which pulls all necessary dependencies from orbit will help -- as long as it has an obvious name. This can then be used with File > Import > Team Project Set to pull the dependencies into the workspace.
The upload widget does a similar thing for it's dependencies. See /cvsroot/rt/org.eclipse.rap/sandbox/org.eclipse.rwt.widgets.upload/rap-sandbox-upload-widget.psf Kind regards, Elias. On Mon, Apr 19, 2010 at 3:25 PM, Austin Riddle <[email protected]> wrote: > Hello, > > I have just completed bug 305278, which adds a dependency in > rwt.visualization.google on the org.json bundle from Orbit that I recently > committed. > > I was going to add it as a package dependency, but I had to override some > behavior that is tied to the current org.json version in Orbit. > > But in either case, a question arises as to how to notify consumers that > they should obtain the Orbit bundle for their convenience (obviously they > could fulfill the dependency themselves, but I don't want them to guess > about how to make the visualizations work). > > Once I commit, their local copies will not compile if they update their > code. So how can we tell them and/or document for new consumers...."Go get > the org.json bundle from Orbit and include it in your target platform and/or > run configuration."? > The incubator webpage? > A README in the bundle? > > Any advice is appreciated. Thanks. > > -- > Austin Riddle > Software Engineer > Computing and Information Technology Division > Texas Center for Applied Technology > Texas Engineering Experiment Station > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev > -- Elias Volanakis | Technical Lead | http://eclipsesource.com [email protected] | +1 503 929 5537 | @evolanakis _______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
