Skip to content

Conversation

FroMage
Copy link
Member

@FroMage FroMage commented Oct 15, 2019

This uses the new info generated by @aloubyansky to display the extension names in the "all config" documentation page.

Part of #3803

ObjectMapper mapper = new ObjectMapper();

// let's read it (and ignore the fields we don't need)
ExtensionJson extensionJson = mapper.readValue(new File(jsonPath), ExtensionJson.class);
Copy link
Member

Choose a reason for hiding this comment

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

I'll provide you with an API to read the "platform json". You have no choice, atm, but, normally, you shouldn't be making assumptions about its format. There will be multiple consumers of that info, so it'll be better to have a common API to read it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Should I wait for this API?

Copy link
Member

Choose a reason for hiding this comment

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

I could open a PR today/tomorrow. If you need it today, I'll do it today.

Copy link
Member

Choose a reason for hiding this comment

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

What you will get is a List<io.quarkus.dependencies.Extension>, which what we've been using to represent extensions described in the JSON so far.

Copy link
Member Author

Choose a reason for hiding this comment

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

That's fine, it can wait for tomorrow, we missed the release train :)

Copy link
Member

@machi1990 machi1990 left a comment

Choose a reason for hiding this comment

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

Hey @FroMage thanks for this great work again :-). I did a quick look at the PR and I have some two comments/questions.

@FroMage
Copy link
Member Author

FroMage commented Oct 16, 2019

I believe this is in good enough shape to make the release unless @gsmet and @cescoffier have started.

@gsmet
Copy link
Member

gsmet commented Oct 16, 2019

@FroMage the release is done. We started early to be able to push to Sonatype before Europe and the US are all pushing artifacts.

@FroMage
Copy link
Member Author

FroMage commented Oct 16, 2019

@gsmet OK, np, it'll wait for next week, thanks.

@FroMage
Copy link
Member Author

FroMage commented Oct 16, 2019

@aloubyansky what do you know of our CI related to the Maven resolving calls fail there? I'm trying to resolve the extension artifacts from Maven, but apparently they haven't been published on CI yet?

@aloubyansky
Copy link
Member

You should be calling it from a mojo initializing MavenArtifactResolver with the Mojo's repo system, session and repos.
Otherwise, does your doc generating process inherits the environment variables?

@FroMage
Copy link
Member Author

FroMage commented Oct 16, 2019

Well, ATM it's in a main program. I didn't want to create a mojo just for that… What environment variables should I pass?

@aloubyansky
Copy link
Member

@FroMage
Copy link
Member Author

FroMage commented Oct 17, 2019

Yeah, that fixed it. ATM the failing test in CI is keycloak, we can ignore it.

@FroMage FroMage marked this pull request as ready for review October 17, 2019 12:48
@FroMage
Copy link
Member Author

FroMage commented Oct 17, 2019

@aloubyansky can we get this in and refactor the extension parsing later?

@aloubyansky
Copy link
Member

aloubyansky commented Oct 17, 2019

I was about to add to my Draft PR and make it non-draft. If yours passes though, i think we can get yours in and i'll adjust it myself.

@FroMage
Copy link
Member Author

FroMage commented Oct 17, 2019

That'd work for me.

@FroMage
Copy link
Member Author

FroMage commented Oct 17, 2019

@gsmet can we merge this? the test failure is keyclock (not related)

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

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

I haven't fully reviewed this one but we need it to make progress so let's merge it now.

@gsmet gsmet merged commit 036219b into quarkusio:master Oct 17, 2019
@gsmet gsmet added this to the 0.26.0 milestone Oct 17, 2019
@FroMage
Copy link
Member Author

FroMage commented Oct 17, 2019

Thanks a lot!

@aloubyansky feel free to refactor this when you merge yours :) Let me know if you need any help!

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.

4 participants