Hi Tammo,

No, I didn't have problems with it. using the mvn eclipse:eclipse, it will
add the generated code as sources, so eclipse clean up the generated byte
code, it will compile these code again as it is being labelled 'source'.
What is your error message here?

In terms of switching to JAXB, I am ok with it, but we need to try it to see
how many changes will it affect.

Regards
Jeff

On Thu, Mar 4, 2010 at 7:18 PM, Tammo van Lessen <[email protected]>wrote:

> Hi Jeff,
>
> XMLBeans habit to not only create java source code but also byte code
> makes, at least to my knowledge, very difficult to work sensibly with
> eclipse, as eclipse periodically cleans up the generated byte code. Did
> you experience the same, do you think it might make sense to drop
> XMLBeans in favor of an alternative (JAXB?)?
>
> Cheers,
>  Tammo
>
>
> On 01.03.2010 17:25, Jeff Yu (JIRA) wrote:
> >
> >      [
> https://issues.apache.org/jira/browse/ODE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Jeff Yu reassigned ODE-766:
> > ---------------------------
> >
> >     Assignee: Jeff Yu
> >
> >> mvn eclipse:eclipse classpath error.
> >> ------------------------------------
> >>
> >>                 Key: ODE-766
> >>                 URL: https://issues.apache.org/jira/browse/ODE-766
> >>             Project: ODE
> >>          Issue Type: Sub-task
> >>          Components: Build System
> >>            Reporter: Jeff Yu
> >>            Assignee: Jeff Yu
> >>             Fix For: 2.0-beta3
> >>
> >>
> >> Three minor issues as following:
> >> 1. javacc maven plugin didn't generate the javacc and jjtree into the
> target/generated folder.
> >> 2. xmlbeans maven plugin didn't generate the classes in the
> target/generated/xmlbeans/
> >> 3. exclude the geronimo-connector-1.1.jar in the il-common module.
> >
>
>
> --
> Tammo van Lessen - http://www.taval.de
>



-- 
Cheers,
Jeff Yu

----------------
blog: http://jeff.familyyu.net

Reply via email to