[jira] Resolved: (CAMEL-3459) Change the dozer Artifact ID from dozer to dozer-osgi - Add camel-dozer to the Jira component list

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-3459.
--------------------------------

    Resolution: Not A Problem
      Assignee: Claus Ibsen

> Change the dozer Artifact ID from dozer to dozer-osgi - Add camel-dozer to the Jira component list
> --------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3459
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3459
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>         Environment: All
>            Reporter: Michael Van Geertruy
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: pom.xml
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Currently dozer releases two versions of its product, dozer (a non-bundled .jar file) and dozer-osgi (an osgi bundle).  Supporting Camel's direction moving to a tighter integration with OSGi, we should use dozer-osgi instead of dozer.  To implement this, change line 44 of the camel-dozer pom.xml document from 
>             <artifactId>dozer</artifactId>
> to
>             <artifactId>dozer-osgi</artifactId>
> This is related to ticket 3228 which is currently in a hold status. Regardless of the changes made to dozer to make it work in OSGi, we will still need to use the dozer-osgi bundle as long as the dozer project creates a seperate bundle. As such, this change should be made prior to the dozer release fixing thier ability to run in Camel.
> I have attached a patched pom.xml file that implements this change

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