On 16/03/2023 9:33 am, Ed Jaffe wrote:
Not true. It simply means if you change the (non-fixed) interface, you
must re-issue all affected components.
OK yes... I did say that you could change the interface with
corresponding pre and co-reqs. And if you just want to change one of the
dependent components, you then need to go back and install the other
fix, and end up changing all the other dependencies, plus anything they
pull in etc...
Not everyone loves chasing pre-req chains in SMP/E. Plus the vendor
needs to track it all somehow and build those chains.
That said, we have been having great luck lately using ++JARUPD
instead of ++JAR for many of our Java-based components and people seem
to like it!
OMG WTF I hadn't discovered ++JARUPD. That sounds like a terrible idea.
Java is a bit of a special case because it is JIT compiled, so you do
get compiler optimizations from inlining etc. But I don't see the point
of partial updates to jar files. You throw away all the checking that
the javac compiler did when it compiled the code, and errors are more
likely to slip through and be discovered by the customer rather than in
the build environment. Even more so now with JPMS, which is complex
enough just building a jar file.
--
Andrew Rowley
Black Hill Software
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
