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

org.springframework.ui.freemarker package move should be documented (along with other similar moves) [SPR-10233] #14866

Closed
spring-projects-issues opened this issue Jan 29, 2013 · 2 comments
Assignees

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jan 29, 2013

Anthony Gerrard opened SPR-10233 and commented

org.springframework.ui.freemarker and a number of other packages that used to reside in spring-context.jar have moved to spring-context-support.jar in 3.2.0. This should be documented.


Affects: 3.2 GA

Reference URL: http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/migration-3.2.html

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Feb 4, 2013

Phil Webb commented

I believe that org.springframework.ui.freemarker has been part of spring-context-support since Spring 3.0:

https://github.com/SpringSource/spring-framework/tree/3.0.x/org.springframework.context.support/src/main/java/org/springframework/ui/freemarker

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Feb 4, 2013

Anthony Gerrard commented

Sorry, I checked on github but must have selected the wrong branch or something. Looking again it was definitely in spring-context-support.jar in 3.1.x. I had to explicitly include spring-context-support.jar after upgrading but I guess this is covered by the “Newly optional dependencies” section on the page.

Apologies - this can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants