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

Provide custom properties mapping in the metadata #775

Open
snicoll opened this issue Nov 22, 2018 · 0 comments
Open

Provide custom properties mapping in the metadata #775

snicoll opened this issue Nov 22, 2018 · 0 comments

Comments

@snicoll
Copy link
Contributor

snicoll commented Nov 22, 2018

Whenever we offer links to the end user, those should eventually match the generation of Spring Boot that you have chosen.

This works fine for Spring Boot as the remote clients can just use that information. However, we have no way to communicate other versions to the user. For instance if we manage the mapping of a library, it would nice that the link to the doc matches the actual version according to the chosen Spring Boot generation.

In the case of Spring Cloud, things are getting much harder as there isn't a consolidated doc per release train. Ideally, we should have links with the release train version in the URL rather than the versions of the individual components as such version isn't exposed to us at the moment.

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

1 participant