How to manage version of plugin?

[angelozerr]

@marijnh I create this issue to know your opinion about version of plugin.

In tern.java I provides several version of dojotoolkit https://github.com/angelozerr/tern.dojotoolkit/tree/master/plugin 1.6, 1.8, 1.9 in other words I have 3 tern plugins dojotoolkit_1.6, dojotoolkit_1.8 and dojotoolkit_1.9.

Today if I want that those plugins can be consumed with tern- system (see https://github.com/marijnh/tern/blob/master/bin/tern#L104), I must create a git project per version. I tell me if it should be possible to improve the load of tern plugin tern- to support version too, in other words I will have one github project tern-dojotoolkit which hosts 3 versions and in the tern-project I could write :

{
  plugin: {dojotoolkit:{version: "1.6"}}
}

instead of writing :

{
  plugin: {dojotoolkit_1.6: {}}
}

@paulvi do you think it's possible to do that with node require?

[marijnh]

Plugin version management is not something that I want to add as a feature to Tern. Just do what you initially described -- create three different plugins. Or, probably better, create a single plugin and allow an option to be passed to it to specify which version of the library to use.

[angelozerr]

Plugin version management is not something that I want to add as a feature to Tern. Just do what you initially described

Thank's @marijnh for your clarification. I will create a github project per version of dojo.

Or, probably better, create a single plugin and allow an option to be passed to it to specify which version of the library to use.

I cannot do that because dojo 1.6 is not based on AMD although 1.8 and 1.9 are based on AMD (tern functions are not the same). More dojo have a big JSON Type Definition, so I'm afraid for performance loading.

[paulvi]

tern functions are not the same

Do you mean there is different entry point inside tern for such cases?

@paulvi do you think it's possible to do that with node require?

require can be used to load module or read json,
while processing json structure is general JavaScript issue.

The structure should be defined by using routines.

My personal hope is please keep it simple

[angelozerr]

Do you mean there is different entry point inside tern for such cases?

dojo 1.6 and dojo 1.8 doesn't manage JS scope with same mean. So we need to create a tern function for 1.6 and1.9. More it's a bad idea to set the 3 JSON Type Definition for dojo in the same JS files. Dojo API is so big.

require can be used to load module or read json,

yes it works like this.

[paulvi]

here is the point that we don't understand each other, and typing messages is not efficient.
Skype me when you have time