beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie ONeil <ekon...@gmail.com>
Subject Re: taking xmlbeans v2 -- was: Re: [jira] Commented: (BEEHIVE-800) Need to upgrade XMLBeans due to binary incompatibility
Date Wed, 22 Jun 2005 14:24:45 GMT
  As of SVN 191756, we're on the v2 release candidate of XMLBeans. 
Once their final release is out, we'll update once more.

  Let me know if you see any problems.

Eddie



On 6/21/05, Eddie ONeil <ekoneil@gmail.com> wrote:
>   Yeah, I've been watching that as well.  Ran through the build /
> tests last night and didn't see any problems with their RC.
> 
>   Unless anyone has a concern about taking the new apache-xbean.jar, I
> was going to get that checked in today.
> 
>   Let me know.
> 
> Eddie
> 
> 
> 
> 
> On 6/21/05, Jacob Danner (JIRA) <beehive-dev@incubator.apache.org> wrote:
> >     [ http://issues.apache.org/jira/browse/BEEHIVE-800?page=comments#action_12314170
]
> >
> > Jacob Danner commented on BEEHIVE-800:
> > --------------------------------------
> >
> > Watching the xmlbeans mailing list, it looks like they are about to vote on a final
V2 candidate in the next couple of days
> >
> > > Need to upgrade XMLBeans due to binary incompatibility
> > > ------------------------------------------------------
> > >
> > >          Key: BEEHIVE-800
> > >          URL: http://issues.apache.org/jira/browse/BEEHIVE-800
> > >      Project: Beehive
> > >         Type: Bug
> > >   Components: Build
> > >     Versions: v1m1
> > >     Reporter: Rich Feit
> > >     Assignee: Rich Feit
> > >     Priority: Blocker
> > >      Fix For: V1
> >
> > >
> > > We need to upgrade to the latest version of XMLBeans, since the project is
making a change that causes binary incompatibility with the one we've got.  This is an email
that went out to the XMLBeans community:
> > > ----
> > > To enable binary compatibility going forward and prevent conflicts with pre-open
sourced usage of XMLBeans, we will change the schema metadata location before our upcoming
v2 release.  The net effect of this change is that current users (including v1 and v2 beta
users) will need to recompile their schemas to enable them to be found correctly.  We apologize
for any inconvenience, and we expect that the new location will remain stable in the future.
> > > ----
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the administrators:
> >    http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> >    http://www.atlassian.com/software/jira
> >
> >
>

Mime
View raw message