-
1. Re: Should we baseline on JDK 5 or JDK 6?
ataylor Sep 28, 2009 5:56 AM (in response to timfox)+1, it also means we can remove some more dependencies, i.e. xerces. Also isn't the AS now java 6 only
-
2. Re: Should we baseline on JDK 5 or JDK 6?
jmesnil Sep 28, 2009 6:11 AM (in response to timfox)+1 to baseline on JDK 6
-
3. Re: Should we baseline on JDK 5 or JDK 6?
clebert.suconic Sep 29, 2009 1:49 PM (in response to timfox)just in case someone missed it (and for future reference), JBoss Branch_5 is now JDK16:
https://jira.jboss.org/jira/browse/JBAS-7293 -
4. Re: Should we baseline on JDK 5 or JDK 6?
apwalker Sep 30, 2009 8:06 PM (in response to timfox)From my observations, one thing to remember is many large corporate’s have only recently moved to JDK 5. Now if your only looking for hornetq adoption through AS then keeping in step with AS is a good approach but if you want to make it easy for wider adoption then JDK 5 support still might be useful.
just my 2cents
Aaron -
5. Re: Should we baseline on JDK 5 or JDK 6?
clebert.suconic Sep 30, 2009 9:54 PM (in response to timfox)Can't we distribute it with JDK 1.6, but keep the source code 1.5 compatible (we could keep a hudson build)? So, case some enterprise customer come and need 1.5 that would still be technically possible.
-
6. Re: Should we baseline on JDK 5 or JDK 6?
plugtree Oct 1, 2009 1:47 AM (in response to timfox)Corporations also look EOL deadlines with fear. I think we can't go wrong with JDK6 (every big iron now has a compatible JDK6 version, i.e. IBM 570, SUN M9000, etc..)
"apwalker" wrote:
From my observations, one thing to remember is many large corporate’s have only recently moved to JDK 5. Now if your only looking for hornetq adoption through AS then keeping in step with AS is a good approach but if you want to make it easy for wider adoption then JDK 5 support still might be useful.
just my 2cents
Aaron -
7. Re: Should we baseline on JDK 5 or JDK 6?
timfox Oct 1, 2009 4:12 AM (in response to timfox)"clebert.suconic@jboss.com" wrote:
Can't we distribute it with JDK 1.6, but keep the source code 1.5 compatible (we could keep a hudson build)? So, case some enterprise customer come and need 1.5 that would still be technically possible.
How does that help?
The whole point of going to Java6 would be to exploit Java6 only code and JDK features. -
8. Re: Should we baseline on JDK 5 or JDK 6?
clebert.suconic Oct 1, 2009 11:21 AM (in response to timfox)It's just that reading the new features description:
http://java.sun.com/javase/6/webnotes/features.html
I get the impression that the biggest improvement for us is performance.
We could use some of the collections stuff.. .and I don't know much how this would affect us in other areas such as Xerces.
I was just thinking the biggest benefit for us would be the runtime, and not so much language features (as it was between 1.4 and 1.5). -
9. Re: Should we baseline on JDK 5 or JDK 6?
timfox Oct 1, 2009 11:23 AM (in response to timfox)But the main performance gain is not by using JDK 6 language features, it's by running with a Java 6 *runtime*
-
10. Re: Should we baseline on JDK 5 or JDK 6?
timfox Oct 1, 2009 11:26 AM (in response to timfox)
Can't we distribute it with JDK 1.6
I don't really understand your point here, we don't distribute a JDK.
It's up to the user to decide what JDK they *run* it with. And currently we recommend Java 6.
This thread is about what level of *code compliance* we use, not which JDK it's run with -
11. Re: Should we baseline on JDK 5 or JDK 6?
clebert.suconic Oct 1, 2009 11:33 AM (in response to timfox)What I was trying to say is that the biggest advantage on JDk 1.6 is the runtime.
I didn't see many advantages on keeping the code as JDK 1.6 only. Maybe I'm blind now. -
12. Re: Should we baseline on JDK 5 or JDK 6?
apwalker Oct 1, 2009 8:30 PM (in response to timfox)I guess the question is if you did baseline on JDK 6 what new APIs would you take advantage of?
Collections? JMX? etc etc....
Also what would be the technical debt if you couldn't use these APIs and have to use another approach.
IMHO if you can justify it I would baseline on JDK 6 but remember enterprise customers are always 1-2 versions behind the current releases and I think you want to keep the barrier to adoption as low as possible.
Correct me if I'm wrong but the current goal for hornetq is to get as many users using it as possible. So unless you have a compelling need for some JDK6 features then just stick with 5.
You can always recommend JDK6+ for performance.
Hope this input is helpful.....