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

Java 5+ upgrade of core container API and implementation [SPR-5231] #9905

Closed
spring-projects-issues opened this issue Oct 22, 2008 · 4 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Juergen Hoeller opened SPR-5231 and commented

Spring 3.0 gives us the chance to upgrade the entire Spring API to Java 5+.

This issue is tracking the upgrade effort in Spring's core packages:

  • org.springframework.aop
  • org.springframework.beans
  • org.springframework.context
  • org.springframework.core
  • org.springframework.util

1 votes, 2 watchers

@spring-projects-issues
Copy link
Collaborator Author

Paul Benedict commented

Will you be introducing generic signatures? Many of these classes still use raw types all over the place.

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Have you been looking at the actual (new) 3.0 repo at https://src.springframework.org/svn/spring-framework/trunk?

We are certainly not done with generifying the API yet... but plenty of it has been generified already.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Two further big commit bunches came in yesterday and tonight. The Java 5 code style update is 99% done now.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Dec 1, 2008

Paul Benedict commented

My apologies. Because this issue was Resolved well in advance of further commits, I thought all the commits were finished. My interest is looking to see how much generic signatures, like #9287, will make it into the core.

For example, this article says that instanceof operator should always use the unknown type <?> on a generic class. I think it's a good practice to follow:
http://mail.openjdk.java.net/pipermail/compiler-dev/2008-November/000714.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants