[jira] Updated: (BUILDR-4) XMLBeans task should use the same XMLBeans version as defined in the project

["Assaf Arkin (JIRA)" <ji...@apache.org>]

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

Assaf Arkin updated BUILDR-4:
-----------------------------

    Attachment: 0002-Now-possible-to-pass-XMLBeans-version-as-options-arg.patch
                0001-Use-buildr.yaml-to-get-version-of-XMLBeans-dependenc.patch

Here's a proposal for addressing this in two ways. First, individually for a project:

  compile_xml_beans ..., :version=>'2.3'

This will run the XML Beans compiler and add the compile dependencies using version 2.3 XML Beans for that project alone.

Second, set it once in the build.yaml file and have Buildr pick on it when loading the XML Beans library:

  xmlbeans: 2.3 

> XMLBeans task should use the same XMLBeans version as defined in the project
> ----------------------------------------------------------------------------
>
>                 Key: BUILDR-4
>                 URL: https://issues.apache.org/jira/browse/BUILDR-4
>             Project: Buildr
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.3
>         Environment: Buildr 1.2.10
>            Reporter: Tammo van Lessen
>            Assignee: Victor Hugo Borja
>             Fix For: 1.3.1
>
>         Attachments: 0001-Use-buildr.yaml-to-get-version-of-XMLBeans-dependenc.patch, 0002-Now-possible-to-pass-XMLBeans-version-as-options-arg.patch
>
>
> I recently upgraded Buildr and ran into some issues with Ode.
> Buildr compiles generated classes with XMLBeans 2.3 but Ode uses XMLBeans 2.2 which is not upward compatible.
> You can reproduce this by compiling the recent ode trunk with Buildr 1.2.10 and then deploying the war into a tomcat.

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