Hi all,

It's out of scope of this issue, but I think tern plugin CordovaJS should be hosted outside tern.java to avoid creating issues in tern.java like I have done
for Tern Dojo Toolkit https://github.com/angelozerr/tern.dojotoolkit, Tern YUI https://github.com/angelozerr/tern.yuidoc

For instance you could create a github project "tern.cordovajs" and add some JS tests like I have done. If you decided to create a github project, I will register to this project to observe changes and copy/paste your CordovaJS tern plugin in tern.java

What do you think about that?

Regards Angelo


2014-05-22 15:55 GMT+02:00 Max Rydahl Andersen <manderse@redhat.com>:
Yeah, we'll unfortunately need to include this update since the
Cordova.js support is important for beta2 work.

/max

> On 05/22/2014 02:19 PM, Victor Rubezhny wrote:
>> In order to fix https://issues.jboss.org/browse/JBIDE-15837 (Improve
>> the
>> CordovaJS library provider), which is Targeted to JBT 4.2.0.Beta2 and
>> depends on https://issues.jboss.org/browse/JBIDE-17317 (Update
>> tern-java
>> plug-ins in target platform 4.40.0.Beta2), we need to make another
>> build
>> for Target Platform to use it (updated TP) for JBT 4.2.0.Beta2.
> As the target-platform is already released, I'm -1 to change the
> target-platform. However, if Max wants to make an exception and want
> this to be in Beta2, we can make an exception and release a new
> 4.40.0.Beta3 target-platform.
> We have 2 options here:
> * Delay JBIDE-15837 to Beta3 and keep using 4.40.0.Beta2 to build
> 4.2.0.Beta2 (current status, no effort)
> * Release a 4.40.0.Beta3 containing the change for tern (amongst
> others), and use it to build 4.2.0.Beta2. Since TP
> 4.40.0.Beta3-SNAPSHOT already contain the change and has been used for
> the last 12 hours already, it may not require much additional
> validation and can be done by the end of the day.
>
> We need to decide that before branching components so that components
> are built and tested against the right target-platform before
> branching.
>
>
> This issues shows that it's not obvious that the target-platform
> changes have an earlier deadline than Code Freeze. For next time,
> we'll try to set up more explicit warnings about the deadlines to get
> dependency change for a given milestone.


/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev