[
https://issues.apache.org/jira/browse/CAMEL-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454744#comment-16454744
]
ASF GitHub Bot commented on CAMEL-10671:
----------------------------------------
dimitrisli commented on issue #2303: CAMEL-10671: Adding Camel example project
for the Ceylon JVM language
URL: https://github.com/apache/camel/pull/2303#issuecomment-384762572
I've done one final polish commit where I've removed unnecessary
dependencies and ensured there is nowhere hardcoded versions. Will look into
squashing all these commits into a single one.
@davsclaus Definitely not a Ceylon expert here as still learning. But my
understanding is: Ceylon [offers an out-of-the-box module system support
built-in the
language](https://ceylon-lang.org/documentation/1.1/reference/structure/module/)
as opposed to Java (pre project Jigsaw) / Kotlin / Scala. This first-class
module system support makes Ceylon module descriptor file(s) obligatory as they
come first and in general there is no need to rely on say Maven/Gradle at all.
In fact Maven support was greatly improved in version 1.3.2 via the Ceylon
Maven plugin to facilitate the up-until-then somehow clunky Ceylon/Java interop
via Maven.
Now on the question 'can we avoid hardcoding the versions in the module
descriptor file' that would saves us from the replace-copy-paste hooks we are
doing here via Maven resources+ant plugins: [It doesn't seem to be the case
based on my Gitter channel
question](https://gitter.im/ceylon/user?at=5adda26e62316e0505eceb43). The best
we can do is [group the same version refs within the module
descriptor](https://gitter.im/ceylon/user?at=5adf0ece2b9dfdbc3ac2bc1c). Also
there is [this somehow 'heated'
discussion](https://github.com/eclipse/ceylon/issues/7030) on why there is the
need to hardcode Maven version dependency numbers in the first place within the
module descriptor.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> camel-example-celyon
> --------------------
>
> Key: CAMEL-10671
> URL: https://issues.apache.org/jira/browse/CAMEL-10671
> Project: Camel
> Issue Type: New Feature
> Components: examples
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
>
> We should have a little example of using camel with celyon. Its just to have
> a maven project with celyon dependencies and compiler setup and some basic
> celyon code that can run standalone with a camel route.
> Take a look at the groovy or kotlin example which would be similar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
