camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gilday (JIRA)" <>
Subject [jira] Commented: (CAMEL-914) Camel Maven plugin should not look for routes in target/test-classes
Date Thu, 18 Sep 2008 10:11:52 GMT


Martin Gilday commented on CAMEL-914:

Thanks Claus,  I will be testing this app over the next few days so it should appear at some
I have updated the wiki about this change.

> Camel Maven plugin should not look for routes in target/test-classes
> --------------------------------------------------------------------
>                 Key: CAMEL-914
>                 URL:
>             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.

View raw message