TaskQueueConfig.localTaskQueueConfig() is not prepared for handling migrated YAML files [138528920]

Fixed

Bug

Status Update

No update yet.

Description

zm...@skawa.hu

created issue #1

Jul 29, 2019 03:17PM

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
Trying to use the task queue configurations I migrated from XMLs to YAMLs based on the guide at

https://cloud.google.com/appengine/docs/standard/java/sdk-gcloud-migration#migrate_config_script in JUnit tests.

What you expected to happen:
I expected that in version 1.9.76 of the appengine-testing library (Java), the local Task Queue's builders are prepared to handle the YAML files created by the migration process, given that the previous, XML-based configuration is being phased out. However, this does not seem to be the case, as the line
TaskQueueConfig.localTaskQueueConfig().setQueueXmlPath("src/main/webapp/WEB-INF/queue.xml") throws a FileNotFound (quite expected, to be honest, since the file IS missing), while the line TaskQueueConfig.localTaskQueueConfig().setQueueXmlPath("src/main/webapp/WEB-INF/queue.yaml") throws a SAXException (also somewhat expected, since it's ... well, not XML).

Steps to reproduce:
Any unit test not using the default task queue should be sufficient, as the queue config file will be missing post-migration.

Other information (workarounds you have tried, documentation consulted, etc):
The migration guide does not detail specific use cases, and the TaskQueueConfig class in the SDK does not seem to contain corresponding functions for setting queue configs from YAML.

Comments

an...@google.com <an...@google.com> #2Jul 30, 2019 09:12AM

Assigned to gc...@google.com.

Sorry for pinging, but jcenter seems to be causing issues again today for many developers.

lu...@google.com <lu...@google.com> Oct 10, 2019 02:21AM

Reassigned to lu...@google.com.

zm...@skawa.hu <zm...@skawa.hu> #3Jan 7, 2020 10:26AM

UAST and intellij-core are licensed under the Apache license which made this easy; trove4j on the other hand is LGPL which makes me more nervous about just repackaging; I'd need to have somebody review what the rules and implications are.

lu...@google.com <lu...@google.com> #4Mar 24, 2020 05:17PM

Accepted by lu...@google.com.

As an alternative to repackaging could you ask Jetbrains to push trove4j to maven central? I don't know the reasoning for why it isn't on there but maybe that's easier.

lu...@google.com <lu...@google.com> #5Apr 15, 2020 06:05PM

Marked as fixed.

Lint in AGP 7.0 / Studio 2020.3 now uses org.jetbrains.intellij.deps:trove4j:1.0.20181211 which is present on maven central.

Issue 138528920