Skip to content
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

Reconsume latest MicroProfile Config 2.0 snapshot #13644

Closed
tevans78 opened this issue Aug 25, 2020 · 5 comments
Closed

Reconsume latest MicroProfile Config 2.0 snapshot #13644

tevans78 opened this issue Aug 25, 2020 · 5 comments

Comments

@tevans78
Copy link
Member

https://repo1.maven.org/maven2/org/eclipse/microprofile/config/microprofile-config-api/2.0-M1/microprofile-config-api-2.0-M1.jar

If the RC1 API is available then we should use that instead

@Azquelt
Copy link
Member

Azquelt commented Sep 3, 2020

With the 2.0 M1 API + a snapshot smallrye impl, we have the following tests failing:

Config 1.2 FAT bucket FULL (from 22 tests):

Config 1.1 FAT bucket FULL (from 314 tests):

@tevans78 tevans78 changed the title Reconsume MicroProfile Config 2.0-M1 API Reconsume latest MicroProfile Config 2.0 snapshot Sep 8, 2020
@tevans78
Copy link
Member Author

tevans78 commented Sep 8, 2020

The tests above have now been disabled so that we can attempt to get into the next beta. Emily and I have been through the failures and there probably isn't anything concerning/unexpected for beta level code.

@tevans78
Copy link
Member Author

tevans78 commented Sep 24, 2020

Using RC1 API and TCK with a snapshot build SmallRye Config, as of 1st Oct, these are now the failing TCKs;
Tests: 368 Failures: 16 Errors: 19

[junit]                                multipleExpressions
[junit]                                defaultExpressionComposedEmpty
[junit]                                noExpressionComposed
[junit]                                arrayEscapes
[junit]                                expressionMissing
[junit]                                noExpression
[junit]                                infiniteExpansion
[junit]                                defaultExpressionComposed
[junit]                                defaultExpression
[junit]                                escape
[junit]                                escapeBraces
[junit]                                composedExpressions
[junit]                                defaultExpressionEmpty
[junit]                                simpleExpression
[junit]                                multipleExpansions
[junit]                                testInjectedConfigSerializable
[junit]                                testConfigProfileWithDev
[junit]                                testConfigPropertiesNoPrefixOnBean
[junit]                                testNoConfigPropertiesAnnotationInjection
[junit]                                testConfigPropertiesWithoutPrefix
[junit]                                testConfigPropertiesPlainInjection
[junit]                                testConfigPropertiesDefaultOnBean
[junit]                                testConfigPropertiesNoPrefixOnBeanThenSupplyPrefix
[junit]                                testConfigPropertiesWithPrefix
[junit]                                testConfigProfileWithDev
[junit]                                testConfigProfileWithDev
[junit]                                expression
[junit]                                expressionNoDefault
[junit]                                testConfigProfileWithDev
[junit]                                configValueInjection
[junit]                                configValueEmpty
[junit]                                configValue
[junit]                                test
[junit]                                testConfigProfileWithDev
[junit]                                testConfigProfileWithDev

@Azquelt
Copy link
Member

Azquelt commented Oct 2, 2020

Running with the latest snapshots of smallrye-config and the TCK, I have the following problems:

Multiple tests have beans which are static inner classes of the test class. The test class and its inner classes are included in the .jar (which has a beans.xml), and then automatically added by arquillian to the .war as well (which has no beans.xml). Liberty sees both classes, makes them beans and then gets an ambiguous bean exception. We might be able to fix this with minimal changes by adding a beans.xml with bean-discovery-mode="none" to the .war so that Liberty doesn't pick up the class in the .war as a bean.

This problem affects multiple classes:

ConfigPropertyFileProfileTest
ProdProfileTest
ConfigProviderTest
InvalidConfigProfileTest
DevConfigProfileTest
ConfigValueTest
TestCustomConfigProfile
TestConfigProfileTest

For PropertyExpressionsTest, expressions do not get resolved because OLSmallRyeConfigProviderResolver.getBuilder() does not add the default interceptors when creating the builder (contrast with SmallRyeConfigProviderResolver).

Once this problem is fixed, PropertyExpressionsTest still fails because the @AfterMethod call runs on both the client and server, and when it runs on the client, the MP Config Impl is not available.

@tevans78
Copy link
Member Author

tevans78 commented Feb 5, 2021

This was completed

@tevans78 tevans78 closed this as completed Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants