Skip to content

Conversation

@labkey-adam
Copy link
Contributor

Rationale

We've had trouble upgrading XMLBeans in the past... added logging may help track down the source of the problem


# sync with Tika/POI
xmlbeansVersion=5.2.0
xmlbeansVersion=5.3.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: On develop, when running gradle commands I'm seeing the XMLBeans version get logged when I don't think i was previously. Here is an example running pickPg:

image

Is this something we're logging? Is it useful? If not, could it be removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@labkey-nicka Yes, we're logging the XMLBeans version in the Gradle Plugins and the server. As the PR comment suggests, we're trying to track down what seems like a version discrepancy between build time and run time. We'll remove the logging once we successfully upgrade.

@labkey-adam
Copy link
Contributor Author

TransformManager test case is failing an XMLBeans enum exception: https://teamcity.labkey.org/buildConfiguration/LabkeyTrunk_Bvt/3341329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants