You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/06/19 12:30:00 UTC

[jira] [Commented] (CAMEL-14818) Incorrect phase for camel-package-maven-plugin in upgrade guide

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

Claus Ibsen commented on CAMEL-14818:
-------------------------------------

There is a camel-component-package-plugin in Camel 3.4 you can use, and dont have to setup a phase

> Incorrect phase for camel-package-maven-plugin in upgrade guide
> ---------------------------------------------------------------
>
>                 Key: CAMEL-14818
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14818
>             Project: Camel
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.1.0
>            Reporter: Jim Cushing
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html]
> As documented, the generated sources for type converter loaders will be created *after* compiling. This means that the type converter loaders will not be available to unit tests, etc. 
> This will go unnoticed if you (or your IDE) previously compiled the source code, thus run the generator. But in a CI environment, the problem is obvious, particularly if you have unit tests that use type converters.
> You can also test with `rm -rf src/generated; mvn install`.
> The solution is to change the phase from `process-classes` to `pre-compile`. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)