[
https://issues.apache.org/activemq/browse/CAMEL-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56078#action_56078
]
Barry Kaplan commented on CAMEL-2167:
-------------------------------------
I don't even know what makes sense for ProcessorDefinitionclass above. I've
tried:
{code}
public abstract class ProcessorDefinition<Type extends ProcessorDefinition>
extends OptionalIdentifiedDefinition<ProcessorDefinition> ...
public abstract class ProcessorDefinition<Type extends ProcessorDefinition>
extends OptionalIdentifiedDefinition<OptionalIdentifiedDefinition> ...
public abstract class ProcessorDefinition<Type extends ProcessorDefinition>
extends OptionalIdentifiedDefinition<Type> ...
{code}
All of which compile with javac but none of which type check with scalac.
> 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.
