Modify behaviour so that failing to provide a JVM server when required generates an error about cics-bundle-maven HOT 5 CLOSED

Hi Dave, DFHWLP might be a sensible default. That is the value used in the Liberty JVM server samples and is shipped with CICS in the pre-defined RDO groups. That said, a warning might make it more obvious that the user hasn't consciously set it. Resolution of such a warning might be to help populate the field with a value of DFHWLP rather than offering blank.

from cics-bundle-maven.

Thanks Ivan - yes we discussed DFHWLP as a default but decided that really if the user was doing Java they needed to set the value to something sensible.

We couldn't get consensus that a majority of users would use DFHWLP a majority of the time, and because of this, and the simplicity of resolving at build time compared to runtime, we opted for forcing the user to specify.

I don't think there will be a way to automatically populate fields because we don't have a custom editor here. However using DFHWLP in our samples could be a better approach than MYJVMS.

from cics-bundle-maven.

Had a further chat with Ivan - we reckon the probability is that a new user would use DFHWLP, customising the name is more advanced.

On that basis we think the ideal is to have an error message that tells them to specify a JVM server (e.g. DFHWLP). If that's hard to do then just updating the default is likely to help a bunch of people who are trying to get started.

from cics-bundle-maven.

Also we should update our samples to use DFHWLP and DFHOSGI as better suggestions.

from cics-bundle-maven.

The JVM server rename is being tracked under #132

from cics-bundle-maven.