*That* is *pity*.
*And* denoying, IMHO *!!!*
I'm copying here the IBM-NetRexx Group, because NetRexx NetRexx is going
*open source*, currently.
You may find all the necessary Links at my *ancient home page*
www.Rexx2Nrx.com
Any questions, just give ibm-netrexx a mail!
Thomas Schneider.
===========================================================
Am 22.11.2010 17:47, schrieb Gregg Wonderly:
> I have a module, for perforce, which I've been supporting since 5.0
> days, and each and every new release of netbeans, I have to create a
> new unique version of the module by simply deleting the dependencies
> on Editor and Editor2 and reinserting them to get the module to
> install without a "the version is not correct" type of error.
>
> I've opened a ticket about this issue in the past. I can't seem to
> find it. At any rate, I just don't understand why this step is
> necessary. If there is no API difference, then why must I do this?
> Wouldn't it be much easier for developers and users to let class
> loading and runtime issues announce API compatibility issues? So much
> of the time, nothing breaks so why is there so much hassle injected
> into the whole idea of modules and plug-ability and the whole
> "platform" concept.
>
> Each new release seems to become a completely separate and new
> platform. For me, this completely breaks the whole idea of a
> "platform". Java doesn't break forward compatibility. It always
> assumes it will work. Why can't netbeans do this do?
>
> Gregg Wonderly
>
--
Thomas Schneider Projects PP, ReyC, and LOGOS on www.KENAI.com
www.thsitc.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Tom. (ths@db-123.com)
Locked
