[jira] [Work logged] (CAMEL-13108) Move mock component out of camel-core

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-13108?focusedWorklogId=192416&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-192416 ]

ASF GitHub Bot logged work on CAMEL-13108:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jan/19 17:02
            Start Date: 30/Jan/19 17:02
    Worklog Time Spent: 10m 
      Work Description: davsclaus commented on pull request #2738: CAMEL-13108: Move mock component out of camel-core
URL: https://github.com/apache/camel/pull/2738
 
 
   Some work to get closer to be able to move mock, dataset and test components out of camel-core. However the builder stuff is tightly coupled to camel-core builder package and would require some more work to find a good way to do this. Will look at this later, but wanted to get this work so far upstream.
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 192416)
            Time Spent: 10m
    Remaining Estimate: 0h

> Move mock component out of camel-core
> -------------------------------------
>
>                 Key: CAMEL-13108
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13108
>             Project: Camel
>          Issue Type: Task
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should likely put mock, dataset and test components in the same JAR as dataset and test extends mock component. So its easier they are in the same JAR.
> Also we already have camel-test for junit testing, so the test component would conflict with camel-test.
> So if we call it camel-mock JAR then we have a free name to use.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)