You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Dennis Byrne <de...@dbyrne.net> on 2006/04/28 21:50:59 UTC
[important] 1.5 in core
There is a call to StringBuffer.insert(int, ILjava/lang/CharSequence;) in JspStateManagerImpl.getPathToComponent . This insert() method was introduced in java 1.5 . Continuum and our compilers have ignored this for months and probably just coerced the second arg into Object.
Are the binaries in the new MyFaces repo being built with the same compiler options as the nightly build process?
This is holding up the release because of a method not found error. I am running low on time right now so I would appreciate it if others can look into this also.
Dennis Byrne
Re: [important] 1.5 in core
Posted by Paul Spencer <pa...@mindspring.com>.
What is the address of the "myfaces repo"?
I do not see a version, or snapshot, dated today in
http://cvs.apache.org/maven-snapshot-repository/org/apache/myfaces/core/.
Paul Spencer
Sean Schofield wrote:
> FYI I put a new RC up on the myfaces repo. TCK testing should begin
> shortly. Lets get this released by the end of the week!
>
> Sean
>
> On 5/1/06, Sean Schofield <se...@gmail.com> wrote:
>
>> Yes we should install JDK 1.4 on the zone which is used for nightly
>> builds and release candidates. I think that is the best long term
>> solution.
>>
>> Sean
>>
>> On 5/1/06, Mario Ivankovits <ma...@ops.co.at> wrote:
>> > Hi!
>> > >> This is holding up the release because of a method not found error.
>> > >> I am running low on time right now so I would appreciate it if
>> others
>> > >> can look into this also.
>> > >
>> > > Which package? Shared or core? I agree, this should be fixed
>> ASAP. I
>> > > will try to find time tomorrow but its better if someone else fix
>> > > first so I can use my time to rebuild the release candidate.
>> > I guess I fixed it, though, not testet but it should do its job.
>> >
>> > It looks like I become the "last bug before release" fixer ;-)
>> >
>> > However, the best will be to use a 1.4 JDK to build the release - or at
>> > least use the JDK 1.4 libraries (this will be possible by adding
>> them to
>> > the bootclasspath I think - I've never done it myself, there are
>> > documentations how to do in internet), that way such incompatibilites
>> > will come up early.
>> >
>> > Ciao,
>> > Mario
>> >
>> >
>>
>
Re: [important] 1.5 in core
Posted by Sean Schofield <se...@gmail.com>.
> What is the address of the "myfaces repo"?
http://myfaces.zones.apache.org/dist/maven-repository/
Re: [important] 1.5 in core
Posted by Paul Spencer <pa...@apache.org>.
What is the address of the "myfaces repo"?
What is the version number in the repo"?
I do not see a version, or snapshot, dated today in
http://cvs.apache.org/maven-snapshot-repository/org/apache/myfaces/core/.
Paul Spencer
Sean Schofield wrote:
> FYI I put a new RC up on the myfaces repo. TCK testing should begin
> shortly. Lets get this released by the end of the week!
>
> Sean
>
> On 5/1/06, Sean Schofield <se...@gmail.com> wrote:
>
>> Yes we should install JDK 1.4 on the zone which is used for nightly
>> builds and release candidates. I think that is the best long term
>> solution.
>>
>> Sean
>>
>> On 5/1/06, Mario Ivankovits <ma...@ops.co.at> wrote:
>> > Hi!
>> > >> This is holding up the release because of a method not found error.
>> > >> I am running low on time right now so I would appreciate it if
>> others
>> > >> can look into this also.
>> > >
>> > > Which package? Shared or core? I agree, this should be fixed
>> ASAP. I
>> > > will try to find time tomorrow but its better if someone else fix
>> > > first so I can use my time to rebuild the release candidate.
>> > I guess I fixed it, though, not testet but it should do its job.
>> >
>> > It looks like I become the "last bug before release" fixer ;-)
>> >
>> > However, the best will be to use a 1.4 JDK to build the release - or at
>> > least use the JDK 1.4 libraries (this will be possible by adding
>> them to
>> > the bootclasspath I think - I've never done it myself, there are
>> > documentations how to do in internet), that way such incompatibilites
>> > will come up early.
>> >
>> > Ciao,
>> > Mario
>> >
>> >
>>
>
Re: [important] 1.5 in core
Posted by Sean Schofield <se...@gmail.com>.
FYI I put a new RC up on the myfaces repo. TCK testing should begin
shortly. Lets get this released by the end of the week!
Sean
On 5/1/06, Sean Schofield <se...@gmail.com> wrote:
> Yes we should install JDK 1.4 on the zone which is used for nightly
> builds and release candidates. I think that is the best long term
> solution.
>
> Sean
>
> On 5/1/06, Mario Ivankovits <ma...@ops.co.at> wrote:
> > Hi!
> > >> This is holding up the release because of a method not found error.
> > >> I am running low on time right now so I would appreciate it if others
> > >> can look into this also.
> > >
> > > Which package? Shared or core? I agree, this should be fixed ASAP. I
> > > will try to find time tomorrow but its better if someone else fix
> > > first so I can use my time to rebuild the release candidate.
> > I guess I fixed it, though, not testet but it should do its job.
> >
> > It looks like I become the "last bug before release" fixer ;-)
> >
> > However, the best will be to use a 1.4 JDK to build the release - or at
> > least use the JDK 1.4 libraries (this will be possible by adding them to
> > the bootclasspath I think - I've never done it myself, there are
> > documentations how to do in internet), that way such incompatibilites
> > will come up early.
> >
> > Ciao,
> > Mario
> >
> >
>
Re: [important] 1.5 in core
Posted by Sean Schofield <se...@gmail.com>.
Yes we should install JDK 1.4 on the zone which is used for nightly
builds and release candidates. I think that is the best long term
solution.
Sean
On 5/1/06, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> >> This is holding up the release because of a method not found error.
> >> I am running low on time right now so I would appreciate it if others
> >> can look into this also.
> >
> > Which package? Shared or core? I agree, this should be fixed ASAP. I
> > will try to find time tomorrow but its better if someone else fix
> > first so I can use my time to rebuild the release candidate.
> I guess I fixed it, though, not testet but it should do its job.
>
> It looks like I become the "last bug before release" fixer ;-)
>
> However, the best will be to use a 1.4 JDK to build the release - or at
> least use the JDK 1.4 libraries (this will be possible by adding them to
> the bootclasspath I think - I've never done it myself, there are
> documentations how to do in internet), that way such incompatibilites
> will come up early.
>
> Ciao,
> Mario
>
>
Re: [important] 1.5 in core
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
>> This is holding up the release because of a method not found error.
>> I am running low on time right now so I would appreciate it if others
>> can look into this also.
>
> Which package? Shared or core? I agree, this should be fixed ASAP. I
> will try to find time tomorrow but its better if someone else fix
> first so I can use my time to rebuild the release candidate.
I guess I fixed it, though, not testet but it should do its job.
It looks like I become the "last bug before release" fixer ;-)
However, the best will be to use a 1.4 JDK to build the release - or at
least use the JDK 1.4 libraries (this will be possible by adding them to
the bootclasspath I think - I've never done it myself, there are
documentations how to do in internet), that way such incompatibilites
will come up early.
Ciao,
Mario
Re: [important] 1.5 in core
Posted by Sean Schofield <se...@gmail.com>.
> There is a call to StringBuffer.insert(int, ILjava/lang/CharSequence;) in JspStateManagerImpl.getPathToComponent . This insert() method was introduced in java 1.5 . Continuum and our compilers have ignored this for months and probably just coerced the second arg into Object.
>
> Are the binaries in the new MyFaces repo being built with the same compiler options as the nightly build process?
Yes the same machine (our zone) but its a 1.5 JDK.
> This is holding up the release because of a method not found error. I am running low on time right now so I would appreciate it if others can look into this also.
Which package? Shared or core? I agree, this should be fixed ASAP.
I will try to find time tomorrow but its better if someone else fix
first so I can use my time to rebuild the release candidate.
> Dennis Byrne
Sean