-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build support for Java language in zAppbuild #468
Comments
Relate to Build support for Java language in DBB |
Thanks for bringing this up. It is the right time to discuss this while we just had some early discussions about it internally especially with the WCA4z assistant. Today, zAppBuild facilitates building ZOS Connect Services as well as CICS Resource Builder definitions - all driving build tasks on USS - which can have a loose dependency to the traditional Cobol / PLI modules. There are various technologies where you can use JAVA on the mainframe, that can be built differently (javac, gradle, maven). What is the particual environment for your java application? How do you build them today, and what are your expectations in terms of managing dependencies? |
Hi @dennis-behm, Thank you for considering my request. The request comes from our development teams who wish to use the Java language for mainframe processing, initially batch processing to manage XML flow exchanges. To date we have never developed in Java on z/OS-USS, nothing committed and everything is to be built. In other development streams, Java projects use Maven. I started looking around and found some information about using IDz and a Java Development Toolkit, but I think I also figured out that the build was done on the workstation and then it was the result of the build, the jar files, which were delivered/deployed to the mainframe. The expected solution is to be able to build and deliver components developed in Java language in the same standard as our traditional applications developed essentially in COBOL. |
Java would not need zAppBuild, nor is zAppBuild geared for Java code. Since Java code can be compiled elsewhere and run on the mainframe, I would advise that you merely deploy the class or jar files. The only reason I can see that you would want to compile on the mainframe is to take advantage of the JZOS API that is built into the IBM SDK for z/OS. |
Hi @Woodsmithkenny, All our mainframe compilation process, (COBOL, Assembler, BMS), already run under USS. The result of the build must also be stored in an Artifactory repository to then be deployed on test and acceptance environments, before being deployed in production. Our mode of operation is to manage the sources under Git, to use DBB to trigger differential builds (and possibly by impacts on dependencies), and the Git commits must be associated with build references (Tags), themselves same associated with the Artifactory packages created following the build. Thanks. |
You can still store in Artifactory, still store code in Git. Also, there is a HUGE difference in how we compile. With Java it's a FULL build every time. You don't recompile just a fraction of it like we do with COBOL or PL/I. With Maven or Gradle, your dependencies are stored within the build file. As far as a compile report, that comes out of javac command. And a Java developer would always (and I mean ALWAYS) compile locally on the workstation regardless of whether they can only execute it on the mainframe. Further, a developer can execute portions of the code using JUnit testing, which can be called as part of every build cycle to ensure quality. |
Hi,
We need to set up a build chain for the Java language on z/OS.
Unless I'm mistaken, Java language support is not implemented in zAppbuild, nor perhaps in the IBM Dependency Based Build APIs, in particular to manage artifacts dependencies.
Is there any work planned for Java language support in zAppbuild (and DBB)?
If we have to develop our own Java language management through zAppbuild, would you have any advice to give us?
Where could we collect information on managing Java compilations in a z/OS environment?
Note that DBB is a Java application for z/OS environment. So the DBB team should have experience on the subject?
Thanks.
The text was updated successfully, but these errors were encountered: