Thank you Tim. You are right about the backward compatibility. I am also using Yenta 1.1 (linked to NB 7.2) with my 11.1 application. It works perfect. However some Maven tools tend to be "too" smart (IntelliJ I see you ;-) and try to retrieve all transitive dependencies.
Apparently RELEASE72 as well as the 8 releases not longer exists and this was the trigger of my question. Maybe we can afford to make the new version of Yenta backward compatible back to 9.0 since this the oldest version available on Apache repo? For older applications, just use Yenta 1.1, don't you think? On Wed, Sep 11, 2019 at 8:37 AM Tim Boudreau <niftin...@gmail.com> wrote: > > I use Jesse's org.netbeans.contrib.yenta plugin to overcome annoying (and > > too restrictive) dependencies in one of my NB based application. However > > Yenta is still linked to NB 7.2. > > > > That version works fine with the latest dev builds. I am using it. > > Bear in mind, with modules, you *want *to set your dependency versions to > the *oldest* version of NetBeans that you can definitely run against. All > setting them higher than that does is restrict people running older > versions from being able to install your plugin for no reason. There is no > reason to update the dependencies of it if it works, and in general, > NetBeans is very, very backward compatible - there are plugins I wrote and > haven't touched for 15 years that I use regularly. > > -Tim >
