camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-914) Camel Maven plugin should not look for routes in target/test-classes
Date Wed, 17 Sep 2008 17:59:52 GMT

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

Claus Ibsen commented on CAMEL-914:
-----------------------------------

Martin I have commited a fix for this. Now the test-classes is not added to the classpath.

Can you test it? You need to use version 1.5-SNAPSHOT of the plugin. And to add the maven
plugin snapshot repo to your maven repo.

{code:xml}
    <pluginRepositories>
        <pluginRepository>
            <id>apache-plugin-snapshots</id>
            <name>Apache Maven Plugins Snapshot Repository</name>
            <url>http://people.apache.org/maven-snapshot-repository</url>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
            <releases>
                <enabled>false</enabled>
            </releases>
        </pluginRepository>
    </pluginRepositories>
{code}

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


Mime
View raw message