Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <1382409201.1221732712593.JavaMail.jira@brutus>
Date: Thu, 18 Sep 2008 03:11:52 -0700 (PDT)
From: "Martin Gilday (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-914) Camel Maven plugin should not look
 for routes in target/test-classes
In-Reply-To: <1016509995.1221654472593.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

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 point.
I have updated the wiki about this change.

> 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.