[
https://issues.apache.org/activemq/browse/CAMEL-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55565#action_55565
]
Hadrian Zbarcea commented on CAMEL-2167:
----------------------------------------
@Claus, I understand how you feel and I share some of it myself. I got
complaints about the ridiculous number of compiler warnings in Camel.
Sometimes they hide real issues (and I found that in a couple of cases). I
agonized over the decision if to go for it or not. It is indicative though of
some level of maturity, or at least it creates a perception of it and I leaned
towards biting the bullet.
Sorry for breaking the scala component, my bad. I guess I owe you guys a beer.
From the fact that you caught it so quickly it seems that you are following
the cutting edge HEAD revision. Which probably means that... I owe you two
beers :). Many thanks!
> 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
> 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.
