Re: [important] 1.5 in core

2006-05-01 Thread Mario Ivankovits
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

2006-05-01 Thread Sean Schofield

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 [EMAIL PROTECTED] 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

2006-05-01 Thread Sean Schofield

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

2006-05-01 Thread Paul Spencer

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

2006-05-01 Thread Sean Schofield

What is the address of the myfaces repo?


http://myfaces.zones.apache.org/dist/maven-repository/


Re: [important] 1.5 in core

2006-05-01 Thread Paul Spencer

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

2006-05-01 Thread Dennis Byrne
I am pretty sure you are looking for myfaces-impl-1.1.3.jar under 
http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/core/myfaces-impl/1.1.3/

The api jar is at an equivalent location.  Sean, this is right?

Thanks for your interest Paul.

Dennis Byrne

-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, May 1, 2006 02:06 PM
To: 'MyFaces Development'
Subject: Re: [important] 1.5 in core

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

2006-05-01 Thread Paul Spencer

Dennis,
Based on Sean's earlier post, you are correct

Some how this got posted twice, probably my fault.

Thank you

Paul Spencer



Dennis Byrne wrote:

I am pretty sure you are looking for myfaces-impl-1.1.3.jar under 
http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/core/myfaces-impl/1.1.3/

The api jar is at an equivalent location.  Sean, this is right?

Thanks for your interest Paul.

Dennis Byrne



-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, May 1, 2006 02:06 PM
To: 'MyFaces Development'
Subject: Re: [important] 1.5 in core

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

2006-04-30 Thread Sean Schofield

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


Re: [important] 1.5 in core

2006-04-30 Thread Dennis Byrne
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.

/pre/ppbroot cause/b prejava.lang.NoSuchMethodError: 
java.lang.StringBuffer.insert(ILjava/lang/CharSequence;)Ljava/lang/StringBuffer;

org.apache.myfaces.application.jsp.JspStateManagerImpl.getPathToComponent(JspStateManagerImpl.java:410)

org.apache.myfaces.application.jsp.JspStateManagerImpl.getPathToComponent(JspStateManagerImpl.java:381)

org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:350)

org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:365)

org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:305)

Sean

I am not saying somone ( probably you Sean ) needs to go through the trouble of 
tag/branch/fix/tag/test/release .  The RC is probably fine and this is just a 
simple argument thrown to the compiler.

Dennis Byrne