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

Martin Gilday commented on CAMEL-914:
-------------------------------------

I have tested the same project and can confirm that it only attempts to load 
routes from target/classes now, which is fantastic.

However I do not see any INFO logging statements about the classpath.  In fact 
one issue is that without a log4j.properties/xml in src/main resources the only 
message that the plugin prints out is:
[INFO] [camel:run]
At first I wasn't even sure if Camel had completed startup.  I think a INFO 
statement saying "Camel route creation complete" or similar would be useful if 
possible.

When I add a log4j config with the root level set to DEBUG you can nicely see 
the details of the routes that are being created.  I will add this to the wiki 
page as it is very useful info to see when prototyping your app.

> Camel Maven plugin should not look for routes in target/test-classes
> --------------------------------------------------------------------
>
>                 Key: CAMEL-914
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-914
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.4.0
>            Reporter: Martin Gilday
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
>
>
> Currently the Maven Plugin attempts to load Camel Routes from both 
> target/classes and target/test-classes.  This causes an issue when you have 
> the same package defined for testing as you have in your Camel Context.  An 
> example problem is using a super class for a test which is only available a 
> test dependency which results in a ClassNotFoundException.
> I would propose one of the following:
> # Prevent the plugin from using target/test-classes altogther
> # Add a mojo parameter to allow for routes under test-classes to be scanned
> #* This should default to False
> #* If this parameter is set to True then the plugin should add dependencies 
> marked as "test" to the classpath

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to