Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of lholmqui@redhat.com
 designates 209.132.183.28 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: new meta data for plugin.xml
From: Lucas Holmquist <lholmqui@redhat.com>
In-Reply-To: 
 <CAMSbhBiuO2VZUTyHzQyey-2wYC5==Tvaaqa3A0zMH9LqD269Wg@mail.gmail.com>
Date: Fri, 18 Oct 2013 08:43:52 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <CBF431D0-AFE4-4AA5-90FF-DFD898453C26@redhat.com>
References: 
 <CAMSbhBiuO2VZUTyHzQyey-2wYC5==Tvaaqa3A0zMH9LqD269Wg@mail.gmail.com>
To: dev@cordova.apache.org


On Oct 17, 2013, at 7:54 PM, Steven Gill <stevengill97@gmail.com> wrote:

> So looks like want to to start including more data on
> http://plugins.cordova.io.
> 
> Repo tag -> points to repo where plugin lives
> Issue tag -> points to issue tracker (with component for jira)
> 
> Testing related (can get discussed more in testing thread
> Mode tag -> to differentiate between testing mode and normal mode
> JS module tag for test module
> 
> Dependency related
> adding version number to dependency tags so they don't just grab latest
> always. Multiple approaches were discussed and this discussion should
> probably happen in a new thread.
> 
> Thoughts on above? Suggestions for other meta data we should look into
> adding to config.xml?
did you mean plugin.xml?