[
https://issues.apache.org/activemq/browse/CAMEL-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56079#action_56079
]
Claus Ibsen commented on CAMEL-2167:
------------------------------------
_rant start_
Barry I am totally with you on java generics. Its a pain in the b*** to use
when its used for a little more than just avoiding ugly type cast.
And on other platforms AIX, HP-UX etc. code that compiles with SUN javac fails
on these platforms. To bad they didnt implemented something that was easier and
ligher. And got those closure in as well. As James Strachan says - javac is
dying.
_rant end_
I have used scala 2.7.7 on trunk and I haven't seen any errors/warns. Do you
see that on trunk? e.g without your patches etc.?
> Upgrade camel-scala to scala 2.8
> --------------------------------
>
> Key: CAMEL-2167
> URL: https://issues.apache.org/activemq/browse/CAMEL-2167
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-scala
> Affects Versions: 2.0.0
> Reporter: Barry Kaplan
> Assignee: Hadrian Zbarcea
> Fix For: 2.2.0, 2.3.0
>
> Attachments: Upgrade_to_scala_2_8.patch
>
>
> The attached patch upgrades to 2.8.0-SNAPSHOT (actually a specific version,
> but pretty close to today).
> Only a few changes were required:
> - Change package declarations to new 2.8 style that allows relative imports
> - Change org.apache.camel.scala.conveters.ScalaTypeConverter from a
> singleton object to a class. Otherwise ObjectHelper failed to instantiate the
> converter due to private access. (This could be 2.8 bug. I will need to raise
> an issue.)
> - Removed generic parameters on references to java classes that were not
> generic. Don't know why this compiled with scala 2.7.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
