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

Document functional configuration style [SPR-15049] #19615

Closed
spring-projects-issues opened this issue Dec 23, 2016 · 3 comments
Closed

Document functional configuration style [SPR-15049] #19615

spring-projects-issues opened this issue Dec 23, 2016 · 3 comments
Assignees
Labels
status: duplicate type: documentation

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Dec 23, 2016

Juergen Hoeller opened SPR-15049 and commented

We need to properly document our functional configuration style and other functional-style facilities in Spring 5.


Issue Links:

  • #19398 Add a functional way to register a bean
  • #19614 Kotlin extension for GenericApplicationContext with registerBean(KClass) variants
  • #19763 Data binding with immutable objects (Kotlin / Lombok / @ConstructorProperties)
  • #19719 Reference documentation for Groovy bean definition DSL
  • #22171 Refactor core documentation to make it relevant for modern Spring applications
@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Oct 4, 2018

Sébastien Deleuze commented

I am wondering if that could be possible to refactor our documentation to avoid the functional API documentation being lost in the existing XML and JavaConfig stuff with something organized like:

  • Section about what is common to XML, JavaConfig and functional beans
  • Section specific to XML
  • Section specific to JavaConfig
  • Section specific to functional beans

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jan 7, 2019

Sébastien Deleuze commented

I have created #22171 which is about what I proposed in the previous comment.

@spring-projects-issues spring-projects-issues added in: core type: task labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.2 RC1 milestone Jan 11, 2019
@jhoeller jhoeller added type: documentation and removed in: core type: task labels Mar 23, 2019
@jhoeller jhoeller removed this from the 5.2 M1 milestone Mar 23, 2019
@jhoeller jhoeller added this to the 5.2 RC1 milestone Mar 23, 2019
@sdeleuze sdeleuze removed this from the 5.2 M3 milestone Jun 7, 2019
@sdeleuze sdeleuze added this to the 5.2 RC1 milestone Jun 7, 2019
@sdeleuze sdeleuze removed this from the 5.2 RC1 milestone Jul 8, 2019
@sdeleuze sdeleuze added this to the 5.2 GA milestone Jul 8, 2019
@sdeleuze sdeleuze removed this from the 5.2 GA milestone Sep 17, 2019
@sdeleuze sdeleuze added this to the 5.3 M1 milestone Sep 17, 2019
@jhoeller jhoeller removed this from the 5.3 M1 milestone Feb 24, 2020
@jhoeller jhoeller added this to the 5.3 M2 milestone Feb 24, 2020
@jhoeller jhoeller removed this from the 5.3 M2 milestone Jun 23, 2020
@jhoeller jhoeller added this to the 5.3 RC1 milestone Jun 23, 2020
@jhoeller jhoeller removed this from the 5.3 RC1 milestone Aug 24, 2020
@jhoeller jhoeller added this to the 5.3 RC2 milestone Aug 24, 2020
@sdeleuze sdeleuze removed this from the 5.3 RC2 milestone Sep 21, 2020
@sdeleuze sdeleuze added this to the 5.3 GA milestone Sep 21, 2020
@sdeleuze
Copy link
Contributor

@sdeleuze sdeleuze commented Oct 25, 2020

Duplicate of #25773.

@sdeleuze sdeleuze added the status: duplicate label Oct 25, 2020
@sdeleuze sdeleuze removed this from the 5.3 GA milestone Oct 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate type: documentation
Projects
None yet
Development

No branches or pull requests

3 participants