You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Edell Nolan (JIRA)" <ji...@apache.org> on 2008/07/03 17:53:00 UTC

[jira] Updated: (SMX4-42) Smx4 camel demo fails because the *itests* directory is missing

     [ https://issues.apache.org/activemq/browse/SMX4-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edell Nolan updated SMX4-42:
----------------------------

    Attachment: camel-assembly.patch
                assembly.patch

Hi,

I have attached two patches 

camel-assembly.patch needs to be applied to Servicmix 3 trunk so that when the demo is included in a kit - it includes the itest directory. 


assembly.patch - includes itests directories so that the demos that have these tests can be built correctly. This should be applied to servicemix 4 freatures trunk.

Taking the old smx3 demos from a 3.3 Snapshot is error prone. We should have these demos on the smx4 trunk with correct versions and updates for smx4. 

The camel demo now builds correctly but fails to deploy for the error thats logged at https://issues.apache.org/activemq/browse/SMX4-44

rgds, Edell.

> Smx4 camel demo fails because the *itests* directory is missing
> ---------------------------------------------------------------
>
>                 Key: SMX4-42
>                 URL: https://issues.apache.org/activemq/browse/SMX4-42
>             Project: ServiceMix 4
>          Issue Type: Bug
>    Affects Versions: 4.0-m2
>            Reporter: Edell Nolan
>         Attachments: assembly.patch, camel-assembly.patch
>
>
> The **/itests/** directories are missing from the demos and causing those demos to fail during their build.
> The assembly descriptors explicitly exclude these directories but these directories don't exist in the 3.3-SNAPSHOT either 
> from where the descriptors take the examples from after unpacking it in its local target dir. 
> So we either need to update the pom's or include these directories.
> Edell.

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