camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kai Wähner (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-5297) Create a new Camel component via Scala-Component-Archetype
Date Mon, 21 May 2012 12:29:41 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280111#comment-13280111
] 

Kai Wähner edited comment on CAMEL-5297 at 5/21/12 12:28 PM:
-------------------------------------------------------------

I added a patch including the archetype and a unit test. It is exactly the same concept as
the java-component-archtype - just with Scala instead of Java.

One TODO is left: The pom.xml contains scala version and plugin version directly instead of
${scala-version} and ${scala-plugin-version}. 

These two properties are used in the camel-scala component already. However, I did not find
out where they are declared ?! I think they must be declared in a parent pom, so that camel-scala
and scala-component-archetype can use them? Can you please solve this TODO when looking at
this patch?

The documentation has to be updated, too (http://camel.apache.org/writing-components.html).
Howevery this should not be done before this feature is added to Camel :-)
                
      was (Author: megachucky):
    Patch including the archetype. It is exactly the same concept as the java-component-archtype
- just with Scala instead of Java.

One TODO is left: The pom.xml contains scala version and plugin version directly instead of
${scala-version} and ${scala-plugin-version}. 

These two properties are used in the camel-scala component already. However, I did not find
out where they are declared ?! I think they must be declared in a parent pom, so that camel-scala
and scala-component-archetype can use them? Can you please solve this TODO when looking at
this patch?

The documentation has to be updated, too (http://camel.apache.org/writing-components.html).
Howevery this should not be done before this feature is added to Camel :-)
                  
> Create a new Camel component via Scala-Component-Archetype
> ----------------------------------------------------------
>
>                 Key: CAMEL-5297
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5297
>             Project: Camel
>          Issue Type: Improvement
>          Components: tooling
>            Reporter: Kai Wähner
>            Priority: Minor
>              Labels: patch
>         Attachments: Component-Scala-Archetype.patch
>
>
> That would be great to have a choice when creating new components. I
> don't think anyone would strongly oppose a component in scala. We already
> have a scala DSL after-all. 
> It makes sense to create components in Scala if the component
> is coupled with Scala in some way. For example the play framework, akka, etc.
> But for other components Java should be prefered, as then anybody in the
> world, can look at the source, and fix bugs, improve stuff etc.
> Also with Scala you force people to add it as dependency etc. And
> there is some binary compatible issues with Scala releases (this may
> improve for the future etc.) And the scala compiler is really slow,
> and the IDE tooling is not so good (yet) etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message