[jira] [Commented] (CB-4494) "plugman search" Should indicate which results are compatible with your configuration

["Tim Kim (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CB-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751716#comment-13751716 ] 

Tim Kim commented on CB-4494:
-----------------------------

Hey all,

I think this is a cool feature but I'm unsure how the check against your configuration would work. With the exception of the cordova-plugman engine, all the other engines (ie, cordova, cordova-ios/android/blackberry etc...) need to execute a version script within the platform directory. However, plugman is supposed to agnostic about the platform directories and it's more of the cli's job to know about that directory in the first place. 

Furthermore, in the case of a custom engine, the version script for the custom engine is to be placed within the plugin's folder so that would mean that having the <engine> version info wouldn't be enough. A user must download the plugin first, run the custom engine version script within the plugin folder, and then determine if it's compatible or not. 



                
> "plugman search" Should indicate which results are compatible with your configuration
> -------------------------------------------------------------------------------------
>
>                 Key: CB-4494
>                 URL: https://issues.apache.org/jira/browse/CB-4494
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Plugman
>            Reporter: Andrew Grieve
>            Assignee: Anis Kadri
>
> I don't think we should filter by your platform, but it would be nice is we had some sort of indicator that showed which results were compatible vs not compatible.
> To do this, we'd need <engine> version info available in the couchdb schema I think.
> Step 1 to this bug is to design, Step 2 is to implement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira