| Pascal -- The entire Callisto community must be thankful that you have provided such a useful plugin. It struck me as exactly the sort of computation/communication we hoped to make widespread with our developer-oriented scripting engine, Eclipse Monkey.
I wonder if you would do me a favor. Could you write in 5 or 10 lines of psudo-code how your plugin does what it does? I ask, not because I can't read java, but because I'm deeply interested in the semantic structures one would wish to have at hand when providing this sort of utility.
I thank you for your effort. I would be glad to clarify my question or explain more about Eclipse Monkey if this would be helpful. Best regards. -- Ward
On May 29, 2006, at 11:32 AM, Pascal Rapicault wrote:
Hi all,
Earlier this year, the eclipse team put together guidelines on how to version plug-ins: http://www.eclipse.org/equinox/documents/plugin-versioning.html.
These guidelines have been adopted by a lot of the callisto teams, however most of them (including the SDK team) missed the fact that specifying properly its version was only part of the problem and that it was equivalently important to specify ranges when requiring plug-ins.
Therefore, in order to help all of you specify the ranges on all the required plug-ins on time for callisto, I have written a little plug-in that will propose values for all the missing ranges. The generated values assume that you are only using APIs however if you know otherwise you should specify a tighter range by lowering the value for the upper bound.
Example of an output:
bundle org.eclipse.cdt.ui <--------- plug-in name which has the problem
org.eclipse.ui.ide;bundle-version="[3.2.0,4.0.0)" <--------- proposed value
org.eclipse.ui.views;bundle-version="[3.2.0,4.0.0)"
org.eclipse.jface.text;bundle-version="[3.2.0,4.0.0)"
org.eclipse.ui.workbench.texteditor;bundle-version="[3.2.0,4.0.0)"
org.eclipse.ui.editors;bundle-version="[3.2.0,4.0.0)"
org.eclipse.ui;bundle-version="[3.2.0,4.0.0)"
org.eclipse.core.resources;bundle-version="[3.2.0,4.0.0)"
org.eclipse.search;bundle-version="[3.2.0,4.0.0)"
org.eclipse.compare;bundle-version="[3.2.0,4.0.0)"
org.eclipse.cdt.core;bundle-version="[3.1.0,4.0.0)"
org.eclipse.ui.console;bundle-version="[3.1.100,4.0.0)"
org.eclipse.core.filebuffers;bundle-version="[3.2.0,4.0.0)"
org.eclipse.core.runtime;bundle-version="[3.2.0,4.0.0)"
org.eclipse.help;bundle-version="[3.2.0,4.0.0)"
How to use the tool:
- copy the attached jar in your plugins folder
- run the following command
java -jar startup.jar -clean -application org.eclipse.core.runtime.versionchecker.dependencyChecker
If you want to only check the dependency for a limited set of plugins, you can specify the -filter option and specify a regexp matching the bundle names. For example "-filter .*cdt.*" will only match the CDT plug-ins.
Regards,
PaScaL
<org_eclipse_core_runtime_versionchecker_1_0_0_jar.DEFANGED-8463> _______________________________________________ cross-project-issues-dev mailing list
|
