You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2006/10/11 03:34:20 UTC
[jira] Resolved: (DIRMINA-278) Provide Java 5 Build
[ http://issues.apache.org/jira/browse/DIRMINA-278?page=all ]
Trustin Lee resolved DIRMINA-278.
---------------------------------
Resolution: Won't Fix
Assignee: Trustin Lee
Actually we are definitely going to move to Java 5 in the next unstable branch. Providing such a alternative build is a good idea, but I think there should be a way for us to manage it without forking the current 1.0.x branch. Please let me know if you have any good idea. My suggestion for you is to wait for the next unstable release: 1.1.0. We should be working on 1.1.0 shortly.
> Provide Java 5 Build
> --------------------
>
> Key: DIRMINA-278
> URL: http://issues.apache.org/jira/browse/DIRMINA-278
> Project: Directory MINA
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0
> Reporter: Graham Miller
> Assigned To: Trustin Lee
>
> Version 1.0 introduced a dependency on backport-util-concurrent. For those of us deploying to a Java 5 platform it is unnecessary to use that library. Could you please provide some way to build the library with the standard Java 5 libraries? Given that backport-util-concurrent is intended to be a drop-in replacement for the Java 5 libraries:
> "The purpose of this library is to enable gradual migration from Java 1.4 to 5.0: the library allows to develop concurrent applications for Java 1.4 that should work with Java 5.0 simply by changing package names." (from http://dcl.mathcs.emory.edu/util/backport-util-concurrent/), perhaps this shouldn't be too hard?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira