> The downside seems to be that the autoupdate code is really hairy and > more complex than what I need initially.
True. But it is one of those modules where it - in my experience - pays off to read the arch doc. ( http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-autoupdate-services/overview-summary.html ) Also, JMeter seems to me like the type of application that would benefit greatly from being build on top of the NetBeans Platform. In fact it is kinda spot on! But that's another discussion. Can't comment on the "wiseness" of your idea, although I fully understand why. I'm guessing that you *may* be able to re-use the AutoUpdate Services part, but the AutoUpdate UI is probably tied very much to the Platform. Just a guess. I could be concerned that the time you'll spend on getting AutoUpdate untangled from NB would be better used to by re-implementing JMeter on top of NB Platform. On Thu, Nov 9, 2017 at 2:07 PM, Emilian Bold <emilian.b...@protonmail.ch> wrote: > Hello, > > Apache JMeter does not have a Plugin Manager and I was thinking of making > one for them. > > They use no module system, just plain Java JARs. > > So, I figured a first step would be to transplant the NetBeans Platform > autoupdate UI and impl, except with a simpler filesystem layout. > > Does this seem wise? > > What I hope to gain is just some dependency resolution, download code and > the update manager UI. Maybe, have a path for a migration to the Platform, > but not necessarily. > > The downside seems to be that the autoupdate code is really hairy and more > complex than what I need initially. > > Anybody tried this before? > > Alternatively: is there some way to use the Platform in a 'hybrid' > classpath + module system mode? I don't think so, but it's worth asking. > > --emi
