In PR #3, I made changes to some xtend files without also committing the changes to their corresponding generated java files. So the new version of the plugin built/published did not include the changes reflected in the xtend files. Apparently, building the AlphaZ plugin from the command line with mvn package does not compile the xtend files. This must be done in Eclipse.
Long term, perhaps we can find a better way to avoid this problem. Either by figuring out how to run the xtend compilation process with maven, and/or adding checks to the PR process here.
Regardless, these changes just include the corresponding java files that I should have included in PR #3.
In PR #3, I made changes to some xtend files without also committing the changes to their corresponding generated java files. So the new version of the plugin built/published did not include the changes reflected in the xtend files. Apparently, building the AlphaZ plugin from the command line with
mvn packagedoes not compile the xtend files. This must be done in Eclipse.Long term, perhaps we can find a better way to avoid this problem. Either by figuring out how to run the xtend compilation process with maven, and/or adding checks to the PR process here.
Regardless, these changes just include the corresponding java files that I should have included in PR #3.