Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 23 May 2012 08:49:40 +0000 (UTC)
From: "Henryk Konsek (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1396147368.10942.1337762981008.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <2136855813.12863.1335868850683.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-5237) Move camel-jibx to camel-extra or
 remove it or whatever
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Henryk Konsek commented on CAMEL-5237:
--------------------------------------

Actually even just now (in the project I'm working in) I've run on the case where I need to use camel-jibx again. I work a lot with high-throughput XML processing (where I make heavy use of Jibx) so I find Jibx data format very useful :) .
                
> Move camel-jibx to camel-extra or remove it or whatever
> -------------------------------------------------------
>
>                 Key: CAMEL-5237
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5237
>             Project: Camel
>          Issue Type: Task
>            Reporter: Claus Ibsen
>             Fix For: 2.10.0, Future
>
>
> The camel-jibx component uses some jibx plugin that cannot find its dependencies in any maven repo, and we get issues when building the source.
> Just getting tired of maintaining this not used component, causing build to fail due artifacts not in reliable maven repos.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira